From: Wu Zhou <woodzltc@cn.ibm.com>
To: Jim Blandy <jimb@redhat.com>
Cc: David Lecomber <david@lecomber.net>, gdb-patches@sources.redhat.com
Subject: Re: [RFC]: Testcase for gdb's handling of Fortran's column-first array
Date: Thu, 03 Nov 2005 16:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.63.0511031354340.7578@linux.site> (raw)
In-Reply-To: <vt2br12syc9.fsf@theseus.home.>
On Wed, 2 Nov 2005, Jim Blandy wrote:
>
> David Lecomber <david@lecomber.net> writes:
> > I've not checked gfortran behaviour -- if it works, it's either because
> > gfortran haven't fixed the original issue, or they changed the
> > expression that we check the 'producer' against before making the swap
> > round (you'll find that in dwarf2readc).
>
> It's worth pointing out that, if the type includes an explicit
> DW_AT_ordering attribute, GDB uses that, and doesn't check the
> producer string at all. So if g77 gets fixed, they could avoid
> running afoul of the "GNU F77" check simply by making their ordering
> explicit.
I just noticed that there is an attribute for array index ordering. It
is very good IMO. But AFAIK, the g77 is not in active development
nowadays. So maybe we can suggest that gfortran developers adopt this so
that gdb could handle it more gracefully.
GFortran developers,
Would anyone of you feel like adding this attribute into your dwarf
output? It is much convenient for gdb to handle the index ordering of
Fortran arrays.
>
> This is still a bit of a kludge: the Dwarf spec says that, in the
> absence of an ordering attribute, the ordering is the default for the
> language. So an explicit "column major" attribute in a Fortran
> compilation unit would be redundant. I only mention it as a way for
> G77 to avoid breaking old GDB's.
>
Regards
- Wu Zhou
next prev parent reply other threads:[~2005-11-03 5:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 7:42 Wu Zhou
2005-11-02 8:58 ` David Lecomber
[not found] ` <vt2br12syc9.fsf@theseus.home.>
2005-11-03 16:09 ` Wu Zhou [this message]
2005-11-03 16:28 ` Wu Zhou
2005-11-14 10:08 ` [Patch ping]: " Wu Zhou
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=Pine.LNX.4.63.0511031354340.7578@linux.site \
--to=woodzltc@cn.ibm.com \
--cc=david@lecomber.net \
--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