From: Yao Qi <qiyaoltc@gmail.com>
To: Keven Boell <keven.boell@linux.intel.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH 1/2] fort_dyn_array: add basic fortran dyn array support
Date: Wed, 20 Jan 2016 10:19:00 -0000 [thread overview]
Message-ID: <86oacgsgdx.fsf@gmail.com> (raw)
In-Reply-To: <5617A6FB.4050407@linux.intel.com> (Keven Boell's message of "Fri, 9 Oct 2015 13:37:31 +0200")
Keven Boell <keven.boell@linux.intel.com> writes:
> Fortran provide types whose values may be dynamically allocated
> or associated with a variable under explicit program control.
> The purpose of this commit is
> * to read allocated/associated DWARF tags and store them in
> the dynamic property list of main_type.
> * enable GDB to print the value of a dynamic array in Fortran
> in case the type is allocated or associated (pointer to
> dynamic array).
>
> Examples:
> (gdb) p vla_not_allocated
> $1 = <not allocated>
>
> (gdb) p vla_allocated
> $1 = (1, 2, 3)
>
> (gdb) p vla_ptr_not_associated
> $1 = <not associated>
>
> (gdb) p vla_ptr_associated
> $1 = (1, 2, 3)
>
> Add basic test coverage for most dynamic array use-cases
> in Fortran.
> The commit contains the following tests:
> * Ensure that values of Fortran dynamic arrays
> can be evaluated correctly in various ways and states.
> * Ensure that Fortran primitives can be evaluated
> correctly when used as a dynamic array.
> * Dynamic arrays passed to subroutines and handled
> in different ways inside the routine.
> * Ensure that the ptype of dynamic arrays in
> Fortran can be printed in GDB correctly.
> * Ensure that dynamic arrays in different states
> (allocated/associated) can be evaluated.
> * Dynamic arrays passed to functions and returned from
> functions.
> * History values of dynamic arrays can be accessed and
> printed again with the correct values.
> * Dynamic array evaluations using MI protocol.
> * Sizeof output of dynamic arrays in various states.
>
> The patch was tested using the test suite on Ubuntu 12.04 64bit.
Hi Keven,
The test cases added by this commit fail on some other OS and targets,
see this thread, https://sourceware.org/ml/gdb-testers/2015-q4/msg02136.html
can you take a look?
--
Yao (齐尧)
next prev parent reply other threads:[~2016-01-20 10:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 12:42 [PATCH 0/2] fort_dyn_array: Enable basic Fortran dynamic " Keven Boell
2015-07-01 12:42 ` [PATCH 2/2] fort_dyn_array: add basic test coverage Keven Boell
2015-07-21 18:19 ` Joel Brobecker
2015-08-05 13:41 ` Keven Boell
2015-07-01 12:42 ` [PATCH 1/2] fort_dyn_array: add basic fortran dyn array support Keven Boell
2015-07-21 18:05 ` Joel Brobecker
2015-08-05 13:41 ` Keven Boell
2015-08-05 13:47 ` Keven Boell
2015-08-05 20:23 ` Joel Brobecker
2015-08-06 11:42 ` keven.boell
2015-08-20 12:52 ` Joel Brobecker
2015-10-09 11:37 ` Keven Boell
2015-10-22 9:59 ` Joel Brobecker
2016-01-20 10:19 ` Yao Qi [this message]
2016-01-22 7:22 ` Keven Boell
2016-01-22 12:40 ` Joel Brobecker
2016-01-22 15:25 ` Yao Qi
2016-01-26 12:34 ` Joel Brobecker
[not found] ` <5613D0DC.3040908@linux.intel.com>
2015-10-22 9:59 ` Joel Brobecker
2015-10-28 15:30 ` off-trunk gdb.fortran/dwarf-stride.exp no longer PASSes [Re: [PATCH 0/2] fort_dyn_array: Enable basic Fortran dynamic array support] Jan Kratochvil
2015-10-28 16:19 ` Jan Kratochvil
[not found] ` <20151028161907.GB4009@adacore.com>
2015-10-30 10:39 ` Jan Kratochvil
2015-11-04 21:48 ` Joel Brobecker
2015-11-04 22:08 ` Jan Kratochvil
2015-11-05 7:31 ` Keven Boell
2015-11-05 8:22 ` Jan Kratochvil
2015-11-05 16:05 ` Keven Boell
2016-02-08 13:47 [PATCH 1/2] fort_dyn_array: add basic fortran dyn array support Walfred Tedeschi
2016-02-09 11:36 ` Joel Brobecker
2016-02-09 15:14 ` Walfred Tedeschi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86oacgsgdx.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=keven.boell@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox