public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alan Modra <amodra@gmail.com>
To: bd1976 llvm <bd1976llvm@gmail.com>
Cc: Fangrui Song <i@maskray.me>, binutils@sourceware.org
Subject: Re: .section directives with the same name but different fields
Date: Mon, 10 Feb 2020 05:21:00 -0000	[thread overview]
Message-ID: <20200210052104.GQ5669@bubble.grove.modra.org> (raw)
In-Reply-To: <CAHYgJu+LHP86sCDGEyDcCAQxDi7NqdHOigBJpWxsM1C1OBJtcQ@mail.gmail.com>

On Thu, Feb 06, 2020 at 05:25:33PM +0000, bd1976 llvm wrote:
> Hi Alan, thanks for the input here. I wonder if it wouldn't be more
> consistent to error in all cases - even in the case of different group
> signatures. The only exception would need to be for the special section
> names (.text, .debug_str, etc...) that the assembler has special knowledge
> of (as you explained).

Yes, let's see how that goes.
https://sourceware.org/ml/binutils/2020-02/msg00129.html

> I wonder why creating multiple sections with the
> same name for section directives with different group signatures was
> implemented - why not just require the use of a distinct section name for
> these?

I think plain ".text" for a group's text section is fine.  Distict
names would just be yet another thing to track for a group.

> Or, now that GNU has the ",unique,N" assembly extension (
> https://sourceware.org/ml/binutils/2020-02/msg00028.html) that could be
> used if the section name is fixed - it would then be explicit in the source
> code that another section with the same name will be created.

Perhaps, but we aren't designing a new toolchain.  Backwards
compatibility can't be discarded without compelling reasons.

-- 
Alan Modra
Australia Development Lab, IBM

  reply	other threads:[~2020-02-10  5:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06  7:38 Fangrui Song
2020-02-06  8:33 ` Alan Modra
2020-02-06  9:19   ` Fangrui Song
2020-02-06 14:09     ` Alan Modra
2020-02-06 17:25       ` bd1976 llvm
2020-02-10  5:21         ` Alan Modra [this message]
2020-03-03 21:20           ` Empty section flags Fangrui Song
2020-04-04 14:17             ` H.J. Lu
2020-04-04 16:38               ` Fangrui Song
2020-04-04 16:45                 ` H.J. Lu
2020-04-13 21:32                   ` Fangrui Song
     [not found]           ` <CAN30aBGpQecmszv-JsZwVTNrOTW0dGt4zUjas7Cx6b-B3XwjgQ@mail.gmail.com>
2020-04-04  0:43             ` Fangrui Song

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=20200210052104.GQ5669@bubble.grove.modra.org \
    --to=amodra@gmail.com \
    --cc=bd1976llvm@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=i@maskray.me \
    /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).