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: Wed, 23 Feb 2005 16:48:00 -0000 [thread overview]
Message-ID: <421C983D.8050201@gnu.org> (raw)
In-Reply-To: <20050221211925.GB14151@lucon.org>
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'.
Andrew
> 2005-02-21 H.J. Lu <hongjiu.lu@intel.com>
>
> * coffcode.h (sec_to_styp_flags): Replaced SEC_CLINK with
> SEC_TIC54X_CLINK. Replace SEC_BLOCK with SEC_TIC54X_BLOCK.
> Replace SEC_SHARED with SEC_COFF_SHARED.
> (styp_to_sec_flags): Likewise.
>
> * elfxx-target.h (TARGET_BIG_SYM): Remove SEC_ARCH_BIT_0.
> (TARGET_LITTLE_SYM): Likewise.
>
> * section.c (SEC_ARCH_BIT_0): Removed.
> (SEC_LINK_DUPLICATES_SAME_CONTENTS): Defined with
> SEC_LINK_DUPLICATES_ONE_ONLY and SEC_LINK_DUPLICATES_SAME_SIZE.
> (SEC_SHARED): Renamed to ...
> (SEC_COFF_SHARED): This.
> (SEC_BLOCK): Renamed to ...
> (SEC_TIC54X_BLOCK): This.
> (SEC_CLINK): Renamed to ...
> (SEC_TIC54X_CLINK): This.
> (SEC_XXX): Rearranged. Move SEC_COFF_SHARED_LIBRARY,
> SEC_COFF_SHARED, SEC_TIC54X_BLOCK and SEC_TIC54X_CLINK to the
> end.
next prev parent reply other threads:[~2005-02-23 14:53 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 [this message]
2005-02-24 1:39 ` H. J. Lu
2005-02-24 16:31 ` Andrew Cagney
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=421C983D.8050201@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).