From: Stan Shebs <shebs@cygnus.com>
To: andy@maxwell.la.asu.edu
Cc: gdb-patches@cygnus.com
Subject: Re: Fortran array patches
Date: Sun, 31 Jan 1999 13:48:00 -0000 [thread overview]
Message-ID: <xdr9sbruul.fsf@andros.cygnus.com> (raw)
Message-ID: <19990131134800.6QdUVtZk1LKcQch6jlnO41vEjI9AUDIrJnqXxnIgG5o@z> (raw)
In-Reply-To: <Pine.SGI.3.96.990104181828.27148A-100000.cygnus.patches.gdb@maxwell.la.asu.edu>
andy@maxwell.la.asu.edu (Andy Vaught) writes:
> Of course, only after the patch has actually been *sent* does an alternate
> explanation occur-- g77 may be at fault! Running gdb on AIX works fine,
> so it looks like g77 is the one that is backwards....
Yes, this particular convention was set up for the benefit of other
Fortran compilers. Craig Burley keeps saying that g77's debug info
generation needs a bunch of work, and not to worry about what GDB
makes of it yet. So if this is important to you, you might want to
consider delving into g77 a bit.
Stan
next parent reply other threads:[~1999-01-31 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SGI.3.96.990104181828.27148A-100000.cygnus.patches.gdb@maxwell.la.asu.edu>
1999-04-01 0:00 ` Stan Shebs [this message]
1999-01-31 13:48 ` Stan Shebs
1999-01-04 18:23 Andy Vaught
1999-04-01 0:00 ` Andy Vaught
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=xdr9sbruul.fsf@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=andy@maxwell.la.asu.edu \
--cc=gdb-patches@cygnus.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