From: Joel Brobecker <brobecker@adacore.com>
To: Chris January <chris.january@allinea.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Support Fortran common blocks with addresses >INT_MAX.
Date: Mon, 12 Mar 2012 15:30:00 -0000 [thread overview]
Message-ID: <20120312153016.GJ2853@adacore.com> (raw)
In-Reply-To: <1331541910.2783.2.camel@gumtree>
> > > 2012-03-08 Chris January <chris.january@allinea.com>
> > >
> > > * stabsread.c (fix_common_block): Change type of valu argument
> > > to CORE_ADDR.
> >
> > This change looks correct to me too. Did you run the testsuite to
> > validate the change, by any chance?
>
> No, although there aren't any test cases in testsuite/gdb.fortran that
> use a common block anyway.
The problem is that this potentially affects more than just Fortran
programs using common blocks.
Would you have a GNU/Linux box available? You could test your change
a little differently, by running the testsuite with -gstabs+. I think
the following command should work:
% make check RUNTESTFLAGS="--target_board % unix/gdb:debug_flags=-gstabs+"
The second issue that this raises is that it would be nice to have
one such testcase to detect future changes that might break this.
But given that this is stabs, and that stabs are on their last breath,
I am not going to insist on it this time around, especially if it is
going to take lots of time from you.
FYI: We, at AdaCore, switch to DWARF on AIX last year. We had to move
to GNU ld for that. One thing I have to say, we're not sorry to be rid
of stabs.
> > Do you have copyright assignment papers on file with the FSF? If not,
> > this change is sufficiently small that we can accept it, as well as
> > your other contribution ("Add another way of setting up [...]").
>
> Yes, we have a company-wide assignment.
OK, found it! Thanks...
--
Joel
next prev parent reply other threads:[~2012-03-12 15:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 14:31 Chris January
2012-03-09 19:39 ` Joel Brobecker
2012-03-12 8:45 ` Chris January
2012-03-12 15:30 ` Joel Brobecker [this message]
2012-03-12 19:30 ` Tom Tromey
2012-03-13 15:17 ` Chris January
2012-03-13 16:50 ` Joel Brobecker
2012-03-12 19:28 ` Tom Tromey
2012-03-08 14:31 Chris January
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=20120312153016.GJ2853@adacore.com \
--to=brobecker@adacore.com \
--cc=chris.january@allinea.com \
--cc=gdb-patches@sourceware.org \
/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