public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "giuliano.belinassi at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/105649] New: Wrong .localentry address on powerpc64le with -fpatchable-function-entry=1 Date: Wed, 18 May 2022 19:56:45 +0000 [thread overview] Message-ID: <bug-105649-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105649 Bug ID: 105649 Summary: Wrong .localentry address on powerpc64le with -fpatchable-function-entry=1 Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: giuliano.belinassi at gmail dot com Target Milestone: --- (this bug triggered PR105647) With the following input file: ``` struct WinsockInterfaceClass { WinsockInterfaceClass(void); virtual int Get_Protocol(void) { return 0; }; }; WinsockInterfaceClass::WinsockInterfaceClass(void) { } ``` Saved as test.C, compiling with > powerpc64le-suse-linux-gcc-11 -c -fpatchable-function-entry=1 test.C Results in the following error: ``` /tmp/cczW6LfZ.s: Assembler messages: /tmp/cczW6LfZ.s:56: Error: .localentry expression for `_ZN21WinsockInterfaceClassC2Ev' is not a valid power of 2 ``` The reason for that maybe is because the addition of nops cause the address of .localentry to be shifted according to how many nops inserted. OTOH > powerpc64le-suse-linux-gcc-11 -c -fpatchable-function-entry=2 test.C works.
next reply other threads:[~2022-05-18 19:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-18 19:56 giuliano.belinassi at gmail dot com [this message] 2022-05-19 6:13 ` [Bug target/105649] " rguenth at gcc dot gnu.org 2022-05-19 13:23 ` giuliano.belinassi at gmail dot com 2022-09-30 12:18 ` cvs-commit at gcc dot gnu.org 2022-09-30 12:34 ` linkw 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-105649-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).