public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Subject: Re: PATCH: Multiple sections with same name don't work
Date: Sat, 01 May 2004 04:34:00 -0000	[thread overview]
Message-ID: <20040501043414.GA23122@lucon.org> (raw)
In-Reply-To: <20040501042506.GS2565@bubble.modra.org>

On Sat, May 01, 2004 at 01:55:06PM +0930, Alan Modra wrote:
> On Fri, Apr 30, 2004 at 08:43:00PM -0700, H. J. Lu wrote:
> > On Sat, May 01, 2004 at 12:29:13PM +0930, Alan Modra wrote:
> > > Actually, it is probably a mistake to try to support multiple sections
> > > of the same name in gas.  For instance, if you have two .text sections,
> > > how is gas supposed to evaluate ".long .text" ?
> > 
> > Will that be generated by compiler? If not, we can issue an error.
> 
> The real question is: Do we need multiple sections of the same name
> in assembly files?  I don't think we do.

The input file may not. But the output should. Otherwise, we have to
change the linker to support section group since it has

  .debug_abbrev   0 : { *(.debug_abbrev) }
  .debug_line     0 : { *(.debug_line) }
  .debug_frame    0 : { *(.debug_frame) }
  .debug_str      0 : { *(.debug_str) }
  .debug_loc      0 : { *(.debug_loc) }
  .debug_macinfo  0 : { *(.debug_macinfo) }



H.J.

  reply	other threads:[~2004-05-01  4:34 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 [this message]
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
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=20040501043414.GA23122@lucon.org \
    --to=hjl@lucon.org \
    --cc=binutils@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).