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/115688] [15 regression] ICE on simple test case from r15-703-gb390b011569635 Date: Fri, 28 Jun 2024 23:32:19 +0000 [thread overview] Message-ID: <bug-115688-4-5ckEqrb5wj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-115688-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115688 --- Comment #6 from Peter Bergner <bergner at gcc dot gnu.org> --- (In reply to Segher Boessenkool from comment #5) > (In reply to Peter Bergner from comment #4) > > That said, how does your patch handle the following test case? > > > > long __attribute__ ((target ("no-altivec,vsx"))) > > foo (void) > > { > > return 0; > > } > > It should hard error for it. That combination is not valid. VSX requires > VMX. Agreed. I think all invalid option combinations should be hard errors. > -mabi={no-,}altivec is only for the 32-bit ABIs. All the 64-bit ABIs had > either only compatible changes to support VMX, or only ever had support for > it in the first place. In that case, -mabi=no-altivec should also be a hard error if -m64 is in effect.
next prev parent reply other threads:[~2024-06-28 23:32 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-27 18:06 [Bug target/115688] New: " bergner at gcc dot gnu.org 2024-06-27 18:07 ` [Bug target/115688] " bergner at gcc dot gnu.org 2024-06-28 1:22 ` linkw at gcc dot gnu.org 2024-06-28 6:26 ` [Bug target/115688] [15 regression] " rguenth at gcc dot gnu.org 2024-06-28 9:07 ` linkw at gcc dot gnu.org 2024-06-28 14:50 ` segher at gcc dot gnu.org 2024-06-28 16:06 ` bergner at gcc dot gnu.org 2024-06-28 18:13 ` segher at gcc dot gnu.org 2024-06-28 23:32 ` bergner at gcc dot gnu.org [this message] 2024-06-30 2:58 ` linkw at gcc dot gnu.org 2024-06-30 3:42 ` 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-115688-4-5ckEqrb5wj@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).