public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: YunQiang Su <wzssyqa@gmail.com>
To: YunQiang Su <yunqiang.su@cipunited.com>
Cc: binutils@sourceware.org, macro@orcam.me.uk
Subject: Re: [PATCH v2] MIPS: Don't move __gnu_lto_slim to .scommon
Date: Wed, 5 Jul 2023 09:42:40 +0800	[thread overview]
Message-ID: <CAKcpw6X_MMjZzZuhCFM4TzcE--Q5tZXz1ZUPKCzt9nNfGy=8ZA@mail.gmail.com> (raw)
In-Reply-To: <20230703105034.3163572-1-yunqiang.su@cipunited.com>

YunQiang Su <yunqiang.su@cipunited.com> 于2023年7月3日周一 18:51写道:
>
> The LTO plugin doesn't expect __gnu_lto_slim is marked as
> COMMOM or moved .scommon section.
>

@Maciej W. Rozycki This is a tiny patch, and I think that it should be
in 2.41 release.
Any idea?

> Let's skip __gnu_lto_slim when detect symbols to be moved to
> .scommon.
>
> This patch can fix testcase:
>         PR ld/15323 (3)
>         PR ld/15323 (4)
> for MIPS.
> ---
>  bfd/elfxx-mips.c | 4 ++++
>  1 file changed, 4 insertions(+)
>
> diff --git a/bfd/elfxx-mips.c b/bfd/elfxx-mips.c
> index 71f2dc9d779..63742de009c 100644
> --- a/bfd/elfxx-mips.c
> +++ b/bfd/elfxx-mips.c
> @@ -7861,6 +7861,10 @@ _bfd_mips_elf_add_symbol_hook (bfd *abfd, struct bfd_link_info *info,
>    switch (sym->st_shndx)
>      {
>      case SHN_COMMON:
> +      /* __gnu_lto_slim shouldn't mark as COMMON and move to .scommon:
> +       lto plugin doesn't expect so.  */
> +      if (strcmp (*namep, "__gnu_lto_slim") == 0)
> +       break;
>        /* Common symbols less than the GP size are automatically
>          treated as SHN_MIPS_SCOMMON symbols.  */
>        if (sym->st_size > elf_gp_size (abfd)
> --
> 2.30.2
>


-- 
YunQiang Su

  reply	other threads:[~2023-07-05  1:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-03 10:36 [PATCH] MIPS: Don't " YunQiang Su
2023-07-03 10:50 ` [PATCH v2] MIPS: Don't move " YunQiang Su
2023-07-05  1:42   ` YunQiang Su [this message]
2023-07-13  5:39     ` YunQiang Su
2023-07-19 14:55     ` Maciej W. Rozycki
2023-07-19 17:26       ` YunQiang Su
2023-07-20  9:05         ` Alan Modra
2023-07-20  9:34           ` Maciej W. Rozycki
2023-07-20 11:23             ` Alan Modra
2023-07-20 14:32               ` Maciej W. Rozycki
2023-07-20 22:44                 ` 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='CAKcpw6X_MMjZzZuhCFM4TzcE--Q5tZXz1ZUPKCzt9nNfGy=8ZA@mail.gmail.com' \
    --to=wzssyqa@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=macro@orcam.me.uk \
    --cc=yunqiang.su@cipunited.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).