public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112980] 64-bit powerpc ELFv2 does not allow nops to be generated before function global entry point Date: Thu, 18 Jan 2024 05:15:36 +0000 [thread overview] Message-ID: <bug-112980-4-d47qrvsYvy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-112980-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112980 Kewen Lin <linkw at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |matz at gcc dot gnu.org Last reconfirmed| |2024-01-18 Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org Ever confirmed|0 |1 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=99888 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> --- [1] made me realize that I forgot to post some comments here. (I thought I did but actually didn't). As Segher's review comments in [2], to support "before NOPs" before global entry and "after NOPs" after global entry, we need to introduce a separate command line option, I think it can be a target specific option, which is enabled by default and we should mention its default behavior and impact in the current documentation for -fpatchable-function-entry. I don't have a good name candidate, any suggestions? Considering that the current behavior aligning with consecutive NOPs looks useless (this request and [1]), an alternative is to aggressively change the current behavior to "before NOPs" before global entry and "after NOPs" after global entry. Any preference or other ideas? Any comments are highly appreciated. I think with either (any) proposal it's inevitable to make the current behavior of -fpatchable-function-entry on "before NOPs" change, we should also document this change in releases/changes.html. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99888#c15 [2] https://gcc.gnu.org/pipermail/gcc-patches/2022-August/600239.html
next prev parent reply other threads:[~2024-01-18 5:15 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-12 9:22 [Bug target/112980] New: " naveen at kernel dot org 2024-01-18 5:15 ` linkw at gcc dot gnu.org [this message] 2024-01-18 9:44 ` [Bug target/112980] " naveen at kernel dot org 2024-01-18 13:36 ` matz at gcc dot gnu.org 2024-01-19 2:06 ` linkw at gcc dot gnu.org 2024-03-19 16:27 ` jamborm at gcc dot gnu.org 2024-03-20 9:05 ` linkw at gcc dot gnu.org 2024-03-25 13:31 ` naveen at kernel dot org 2024-04-01 7:30 ` linkw at gcc dot gnu.org 2024-04-01 14:03 ` giuliano.belinassi at gmail dot com 2024-04-02 8:21 ` linkw at gcc dot gnu.org 2024-04-02 8:24 ` linkw at gcc dot gnu.org 2024-04-04 18:24 ` giuliano.belinassi at gmail dot com 2024-04-09 3:02 ` linkw at gcc dot gnu.org 2024-04-09 12:59 ` matz at gcc dot gnu.org 2024-04-10 2:14 ` linkw at gcc dot gnu.org 2024-04-11 12:37 ` matz at gcc dot gnu.org 2024-04-12 3:48 ` linkw at gcc dot gnu.org 2024-05-29 2:21 ` 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-112980-4-d47qrvsYvy@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).