All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: sparclinux@vger.kernel.org
Subject: Re: [PATCH] sparc: Fix invalid .section syntax
Date: Fri, 16 Jun 2023 18:56:42 +0200	[thread overview]
Message-ID: <20230616165642.GD1697490@ravnborg.org> (raw)
In-Reply-To: <ZIyBGdriWti6AsvH@decadent.org.uk>

Hi Ben,

On Fri, Jun 16, 2023 at 05:34:49PM +0200, Ben Hutchings wrote:
> From: Ben Hutchings <benh@debian.org>
> 
> gas supports several different forms for .section for ELF targets,
> including:
>     .section NAME [, "FLAGS"[, @TYPE[,FLAG_SPECIFIC_ARGUMENTS]]]
> and:
>     .section "NAME"[, #FLAGS...]
> 
> In several places we use a mix of these two forms:
>     .section NAME, #FLAGS...
> 
> A current development snapshot of binutils (2.40.50.20230611) treats
> this mixed syntax as an error.
> 
> Change to consistently use:
>     .section NAME, "FLAGS"
> as is used elsewhere in the kernel.
> 
> Also change the one correct use of:
>     .section "NAME", #FLAGS
> to be consistent with the rest of the kernel.

The commit also changes from the solaris compatibility names to the
standard gas names.
The change surprised me while reading the patch, and I was not happy
until I found out that the current flags are compatibility names.
So please add this info to the changelog.

With that fixed:
Reviewed-by: Sam Ravnborg <sam@ravnborg.org>

I expect someone else to pick it up.

	Sam

      parent reply	other threads:[~2023-06-16 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-16 15:34 [PATCH] sparc: Fix invalid .section syntax Ben Hutchings
2023-06-16 15:45 ` Ben Hutchings
2023-06-16 16:56 ` Sam Ravnborg [this message]

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=20230616165642.GD1697490@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=ben@decadent.org.uk \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.