public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Fangrui Song <maskray@google.com>
Cc: binutils@sourceware.org, "H.J. Lu" <hjl.tools@gmail.com>
Subject: Re: [PATCH] ld: Allow R_X86_64_GOTPCREL for call *__tls_get_addr@GOTPCREL(%rip)
Date: Thu, 2 Mar 2023 12:37:39 +0100	[thread overview]
Message-ID: <2c693059-fcc0-0874-68be-47bbfef47260@suse.com> (raw)
In-Reply-To: <20230105210542.3573076-1-maskray@google.com>

On 05.01.2023 22:05, Fangrui Song via Binutils wrote:
> _Thread_local int a;
> int main() { return a; }
> 
> % gcc -fno-plt -fpic a.c -fuse-ld=bfd -Wa,-mrelax-relocations=no
> /usr/bin/ld.bfd: /tmp/ccSSBgrg.o: TLS transition from R_X86_64_TLSGD to R_X86_64_GOTTPOFF against `a' at 0xd in section `.text' failed
> /usr/bin/ld.bfd: failed to set dynamic section sizes: bad value
> collect2: error: ld returned 1 exit status
> 
> This commit fixes the issue.

The discussion with H.J. looks to have died out, without a clear result.
May I suggest the following (also for the other, 32-bit patch): You
extend the description to address H.J.'s concerns verbally, and unless
he comes forward pointing actual flaws in here, I'd then intend to
approve the changes.

Jan

>     PR ld/24784
>     * bfd/elf64-x86-64.c (elf_x86_64_check_tls_transition): Allow
>       R_X86_64_GOTPCREL.
> ---
>  bfd/elf64-x86-64.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/bfd/elf64-x86-64.c b/bfd/elf64-x86-64.c
> index 914f82d0151..095fe2e0fe6 100644
> --- a/bfd/elf64-x86-64.c
> +++ b/bfd/elf64-x86-64.c
> @@ -1241,7 +1241,7 @@ elf_x86_64_check_tls_transition (bfd *abfd,
>  	  if (largepic)
>  	    return r_type == R_X86_64_PLTOFF64;
>  	  else if (indirect_call)
> -	    return r_type == R_X86_64_GOTPCRELX;
> +	    return (r_type == R_X86_64_GOTPCRELX || r_type == R_X86_64_GOTPCREL);
>  	  else
>  	    return (r_type == R_X86_64_PC32 || r_type == R_X86_64_PLT32);
>  	}


  parent reply	other threads:[~2023-03-02 11:37 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 21:05 Fangrui Song
2023-01-06 17:03 ` H.J. Lu
2023-01-06 18:48   ` Fangrui Song
2023-01-06 21:13     ` H.J. Lu
2023-01-06 21:25       ` Fangrui Song
2023-01-06 21:26         ` H.J. Lu
2023-01-06 21:44           ` Fangrui Song
2023-01-06 22:41             ` H.J. Lu
2023-01-06 23:02               ` Fangrui Song
2023-01-06 23:20                 ` H.J. Lu
2023-01-06 23:52                   ` Fangrui Song
2023-01-07  0:01                     ` H.J. Lu
2023-01-09  8:15   ` Jan Beulich
2023-01-09 21:14     ` H.J. Lu
2023-01-10  9:16       ` Jan Beulich
2023-01-10 20:39         ` H.J. Lu
2023-01-10 21:02           ` Fangrui Song
2023-01-11  9:01             ` Jan Beulich
2023-01-11  8:10           ` Jan Beulich
2023-03-02 11:37 ` Jan Beulich [this message]
2023-03-02 20:10   ` [PATCH v2] " Fangrui Song
2023-03-10  9:10     ` Jan Beulich

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=2c693059-fcc0-0874-68be-47bbfef47260@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --cc=maskray@google.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).