public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114759] Power: multiple issues with -mrop-protect Date: Thu, 18 Apr 2024 02:15:13 +0000 [thread overview] Message-ID: <bug-114759-4-T0HrZrRGWm@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114759-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114759 --- Comment #4 from Peter Bergner <bergner at gcc dot gnu.org> --- Created attachment 57977 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57977&action=edit Patch that emits an error for invalid ROP option combinations. Here's a patch that treats invalid ROP option combinations (currently assuming P7 and earlier are invalid) as an error. If instead we want to just silently ignore (or with a warning), we'd just need to modify the rs6000.cc hunk to disable rs6000_rop_protect instead of calling error().
next prev parent reply other threads:[~2024-04-18 2:15 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-17 21:18 [Bug target/114759] New: " bergner at gcc dot gnu.org 2024-04-17 21:19 ` [Bug target/114759] " bergner at gcc dot gnu.org 2024-04-17 22:39 ` segher at gcc dot gnu.org 2024-04-18 0:56 ` bergner at gcc dot gnu.org 2024-04-18 2:15 ` bergner at gcc dot gnu.org [this message] 2024-04-18 2:24 ` bergner at gcc dot gnu.org 2024-06-18 23:09 ` bergner at gcc dot gnu.org 2024-06-19 22:03 ` bergner 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-114759-4-T0HrZrRGWm@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).