public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106834] GCC creates R_X86_64_GOTOFF64 for 4-bytes immediate Date: Mon, 05 Sep 2022 08:49:29 +0000 [thread overview] Message-ID: <bug-106834-4-vRXq9BGumB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106834-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106834 Alexander Monakov <amonakov at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |amonakov at gcc dot gnu.org --- Comment #2 from Alexander Monakov <amonakov at gcc dot gnu.org> --- Can you show how gcc -S output looks for you on this testcase? For me the problematic instruction is just movl $_GLOBAL_OFFSET_TABLE_, %eax or leaq _GLOBAL_OFFSET_TABLE_(%rip), %rax with -fpie, so it's the assembler who chooses the relocation type (which would make that a Binutils bug).
next prev parent reply other threads:[~2022-09-05 8:49 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-05 8:15 [Bug c++/106834] New: " rui314 at gmail dot com 2022-09-05 8:17 ` [Bug c++/106834] " rui314 at gmail dot com 2022-09-05 8:49 ` amonakov at gcc dot gnu.org [this message] 2022-09-05 8:54 ` rui314 at gmail dot com 2022-09-05 9:38 ` amonakov at gcc dot gnu.org 2022-09-05 10:24 ` marxin at gcc dot gnu.org 2022-09-05 11:20 ` amonakov at gcc dot gnu.org 2022-09-05 11:39 ` marxin at gcc dot gnu.org 2022-09-05 11:53 ` amonakov at gcc dot gnu.org 2022-09-05 16:35 ` [Bug target/106834] " hjl.tools at gmail dot com 2022-09-05 21:17 ` amonakov at gcc dot gnu.org 2022-09-06 15:54 ` hjl.tools at gmail dot com 2022-09-06 17:53 ` hjl.tools at gmail dot com 2022-10-21 5:17 ` pinskia at gcc dot gnu.org
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=bug-106834-4-vRXq9BGumB@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).