From: Zack Weinberg <zack@codesourcery.com>
To: "H. J. Lu" <hjl@gcc.gnu.org>
Cc: binutils@sources.redhat.com
Subject: Re: PATCH: Multiple sections with same name don't work
Date: Sat, 01 May 2004 18:42:00 -0000 [thread overview]
Message-ID: <87wu3wrnu5.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <20040501144439.GU2565@bubble.modra.org> (Alan Modra's message of "Sun, 2 May 2004 00:14:39 +0930")
Alan Modra <amodra@bigpond.net.au> writes:
> On Sat, May 01, 2004 at 12:06:18AM -0700, H. J. Lu wrote:
>> On Fri, Apr 30, 2004 at 10:50:08PM -0700, H. J. Lu wrote:
>> > On Fri, Apr 30, 2004 at 10:12:01PM -0700, Zack Weinberg wrote:
>> > > Alan Modra <amodra@bigpond.net.au> writes:
>> > > > The real question is: Do we need multiple sections of the same name
>> > > > in assembly files? I don't think we do.
>> > >
>> > > I need them in order to generate COMDAT sections compatible with the
>> > > HPUX linker. gcc might emit e.g.
>> > >
>> > > .section .text
>> > > # non-COMDAT code ...
>> > >
>> > > .section .text,"G",symbol_name,comdat
>> > > # code for symbol_name ...
>
> Hmm, it wouldn't be much harder to use
>
> .section .text.symbol_name,"G",symbol_name,comdat
> # code for symbol_name ...
That may not work. Unfortunately, the HPUX linker's COMDAT-group
support is only partially documented, and subtly incompatible with the
standard ELF SHT_GROUP notion. I am having to work things out by
reverse engineering what aCC does -- and it uses multiple sections
with the same name.
zw
next prev parent reply other threads:[~2004-05-01 18:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 22:31 H. J. Lu
[not found] ` <20040430230129.GA17907@lucon.org>
2004-05-01 0:36 ` PATCH: " H. J. Lu
2004-05-01 2:31 ` Alan Modra
2004-05-01 2:59 ` Alan Modra
2004-05-01 3:43 ` H. J. Lu
2004-05-01 4:25 ` Alan Modra
2004-05-01 4:34 ` H. J. Lu
2004-05-01 5:12 ` Zack Weinberg
2004-05-01 5:50 ` H. J. Lu
2004-05-01 7:06 ` H. J. Lu
2004-05-01 14:44 ` Alan Modra
2004-05-01 15:37 ` H. J. Lu
2004-05-01 17:31 ` H. J. Lu
2004-05-01 18:42 ` Zack Weinberg [this message]
2004-05-01 7:08 ` H. J. Lu
2004-05-11 15:57 Nick Clifton
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=87wu3wrnu5.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=binutils@sources.redhat.com \
--cc=hjl@gcc.gnu.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).