Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@lecomber.net>
To: Wu Zhou <woodzltc@cn.ibm.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC]: Testcase for gdb's handling of Fortran's column-first array
Date: Wed, 02 Nov 2005 08:58:00 -0000	[thread overview]
Message-ID: <1130918595.9928.22.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0511021352240.4720@linux.site>


> OK.  With all these said, here is the patch.  I had tested it on FC4, it 
> reported no failure.  But however I _did_ found a old gdb (6.1 maybe) 
> handle this incorrectly.  So this testcase still make senses.  OK to 
> commit?


Hi Wu

That's what I'd expect, as my patch to fix things went in to GDB 6.2.1
(iirc).  

One thing to note is that g77 puts things the wrong way round in the
symbol table (but not in the real data).  In the dwarf2 reader we have
an explicit fix for this incorrect GNU behaviour, but you will not find
the same fix in stabs or dwarf1 -- so on legacy platforms (AIX, Solaris)
with g77 you should expect failure with GNU, pass with IBM's XLF and
Sun's Forte.  

It's also going to fail on Linux with -gstabs as a parameter for g77.  

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).

Cheers
d.
-- 
David Lecomber <david@lecomber.net>


  reply	other threads:[~2005-11-02  7:42 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 [this message]
     [not found]   ` <vt2br12syc9.fsf@theseus.home.>
2005-11-03 16:09     ` Wu Zhou
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=1130918595.9928.22.camel@cpc2-oxfd8-3-0-cust199.oxfd.cable.ntl.com \
    --to=david@lecomber.net \
    --cc=gdb-patches@sources.redhat.com \
    --cc=woodzltc@cn.ibm.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