From: Andrew Cagney <cagney@gnu.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com
Subject: Re: PATCH: Rearrange SEC_XXX bits
Date: Thu, 24 Feb 2005 16:31:00 -0000 [thread overview]
Message-ID: <421DDCC3.500@gnu.org> (raw)
In-Reply-To: <20050223194053.GA31025@lucon.org>
H. J. Lu wrote:
> On Wed, Feb 23, 2005 at 09:50:37AM -0500, Andrew Cagney wrote:
>
>>H. J. Lu wrote:
>>
>>>We have very limited space in BFD section flag. But SEC_ARCH_BIT_0 is
>>>never used. There are also some COFF and TI specific bits. This patch
>>>removes SEC_ARCH_BIT_0 and makes COFF/TI specific bits for COFF/TI
>>>only so that other format/target can reuse those bits.
>>
>>FYI, this looks to break gdb's dump.exp testcase (that test writes out
>>then reads back random object file formats verifying the result). Right
>>now I consider this 'weird'.
>>
>
>
> I don't see how my patch should change anything.
Like I said, 'weird'. It does point to this being an ABI change - any
any solib version number needs to be rolled.
> In any case, I got
>
> Running /export/gnu/src/gdb/gdb/gdb/testsuite/gdb.base/detach.exp ...
> Running /export/gnu/src/gdb/gdb/gdb/testsuite/gdb.base/display.exp ...
> Running /export/gnu/src/gdb/gdb/gdb/testsuite/gdb.base/dump.exp ...
> Running /export/gnu/src/gdb/gdb/gdb/testsuite/gdb.base/echo.exp ...
>
> It looks fine to me.
That's because I found / fixed the [gdb] bug ;-)
Andrew
next prev parent reply other threads:[~2005-02-24 13:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 0:29 H. J. Lu
2005-02-22 0:43 ` H. J. Lu
2005-02-22 4:23 ` Alan Modra
2005-02-23 16:48 ` Andrew Cagney
2005-02-24 1:39 ` H. J. Lu
2005-02-24 16:31 ` Andrew Cagney [this message]
2005-02-24 16:45 ` Alan Modra
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=421DDCC3.500@gnu.org \
--to=cagney@gnu.org \
--cc=binutils@sources.redhat.com \
--cc=hjl@lucon.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).