public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thiago at kde dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/99530] New: [i386] 'P' inline assembly operand modifier should obey -fno-plt Date: Wed, 10 Mar 2021 21:51:23 +0000 [thread overview] Message-ID: <bug-99530-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99530 Bug ID: 99530 Summary: [i386] 'P' inline assembly operand modifier should obey -fno-plt Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: thiago at kde dot org Target Milestone: --- $ cat test.c extern void f(void); void g() { asm("call %P0 ; asm" : : "X" (f)); } int h() { f(); return 0; } The normal modes work: $ gcc -fno-pic -S -o - -O2 test.c| grep call call f ; asm call f $ gcc -fPIC -S -o - -O2 test.c| grep call call f@PLT ; asm call f@PLT But the -fno-plt modes still generate PLT references: $ gcc -fno-pic -fno-plt -S -o - -O2 test.c| grep call call f ; asm call *f@GOTPCREL(%rip) $ gcc -fPIC -fno-plt -S -o - -O2 test.c| grep call call f@PLT ; asm call *f@GOTPCREL(%rip)
next reply other threads:[~2021-03-10 21:51 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 21:51 thiago at kde dot org [this message] 2021-03-10 22:04 ` [Bug target/99530] " thiago at kde dot org 2021-03-11 13:31 ` hjl.tools at gmail dot com 2021-03-11 15:02 ` hjl.tools at gmail dot com 2021-03-11 16:00 ` thiago at kde dot org 2021-03-11 16:01 ` thiago at kde dot org 2021-03-11 16:06 ` thiago at kde dot org 2021-03-11 19:02 ` hjl.tools at gmail dot com 2021-03-11 21:03 ` thiago at kde dot org 2021-03-11 21:53 ` hjl.tools at gmail dot com 2021-03-11 22:14 ` thiago at kde dot org 2021-03-11 22:27 ` hjl.tools at gmail dot com 2021-03-11 22:28 ` hjl.tools at gmail dot com 2021-03-11 22:38 ` thiago at kde dot org 2021-03-13 16:42 ` hjl.tools at gmail dot com 2021-03-17 14:32 ` hjl.tools at gmail dot com
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-99530-4@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).