From: David Lecomber <david@streamline-computing.com>
To: Jim Blandy <jimb@redhat.com>
Cc: patches <gdb-patches@sources.redhat.com>
Subject: Re: [PATCH/RFA] PR gdb/648
Date: Mon, 16 Aug 2004 12:33:00 -0000 [thread overview]
Message-ID: <1092659613.5816.0.camel@localhost> (raw)
In-Reply-To: <vt24qn6wuy2.fsf@zenia.home>
On Fri, 2004-08-13 at 23:10, Jim Blandy wrote:
> David Lecomber <david@streamline-computing.com> writes:
> > 2004-08-06 David Lecomber <dsl@sources.redhat.com>
> >
> > Fix PR gdb/648
> > * dwarf2read.c (read_array_type): Handle column major arrays
> > correctly. Assume column major for Fortran except with G77
> > compiler.
> > * eval.c (evaluate_subexp_standard): Assume Fortran arrays are
> > oriented large to small in type structure.
>
> Thanks very much for the patch and test program. It was helpful to be
> able to actually look at what GNU F77 was producing for a real Fortran
> program.
>
> For the dwarf2read.c part, I think the essential approach is fine.
> However:
>
> - Rather than recognizing Fortran specially in read_array_type, I'd
> rather have a new member of 'struct language_defn' giving the array
> ordering for that language.
>
> - I'd like to have the logic that chooses a byte order pulled out of
> read_array_type into its own function that takes a die, a cu, and
> returns a DW_ORD_ value. That function would take care of looking
> for a DW_AT_ordering attribute, recognizing the appropriate versions
> of GNU F77, and so on. read_array_type should call that function
> and build the type appropriately.
next prev parent reply other threads:[~2004-08-16 12:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 22:10 David Lecomber
2004-08-13 10:25 ` David Lecomber
2004-08-13 10:32 ` Michael Chastain
2004-08-13 22:14 ` Jim Blandy
2004-08-16 12:33 ` David Lecomber [this message]
2004-08-16 12:38 ` David Lecomber
2004-08-18 16:36 ` Jim Blandy
2004-08-20 13:37 ` [PATCH/RFA] PR gdb/648 (eval.c approval reqd) David Lecomber
2004-08-20 13:45 ` David Lecomber
2004-08-25 5:53 ` Jim Blandy
2004-08-25 7:24 ` David Lecomber
2004-08-27 0:00 ` Jim Blandy
2004-08-27 9:15 ` David Lecomber
2004-08-27 13:52 ` Andrew Cagney
2004-08-27 13:58 ` Michael Chastain
2004-08-27 14:14 ` Andrew Cagney
2004-08-27 14:57 ` Michael Chastain
2004-08-27 15:57 ` Andrew Cagney
2004-08-27 16:15 ` Michael Chastain
2004-08-30 14:17 ` Andrew Cagney
2004-08-23 19:26 ` [PATCH/RFA] PR gdb/648 Andrew Cagney
2004-08-24 18:03 ` Jim Blandy
2004-08-15 8:19 ` Michael Chastain
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=1092659613.5816.0.camel@localhost \
--to=david@streamline-computing.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.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