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/113652] [14 regression] Failed bootstrap on ppc unrecognized opcode: `lfiwzx' with -mcpu=7450 Date: Tue, 30 Jan 2024 03:05:37 +0000 [thread overview] Message-ID: <bug-113652-4-VPyHk6d13j@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113652-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113652 --- Comment #6 from Kewen Lin <linkw at gcc dot gnu.org> --- I think this is related to r10-580-ge154242724b084 and this failure is expected and a use error. With it applied, we don't always pass -many to assembler with CHECKING_P enabled. Actually compilers (gcc-13, gcc-12, gcc-11 or trunk) generate the same assembly, but because gcc-11/gcc-12/gcc-13 is built with --checking=release by default which doesn't set CHECKING_P while trunk is built with --checking=yes,extra by default which set CHECKING_P. So it causes the different behaviors so that further considered as regression unexpectedly. The issue should be gone if trunk gets released as gcc-14 or it's built with --checking=release. IMO Alan's commit aims to help to expose more and more such unexpected use cases and users can fix them in place. As #c3 "PowerPC 7450 (aka PowerPC G4) is only capable of -maltivec but not -mvsx", so it's unexpected to have -mcpu=7450 meanwhile having -mvsx, could you check where the -mvsx comes from and fix it instead? Thanks! btw, a workaround option is to add -Wa,-many to restore the previous behavior that passing -many to assembler.
next prev parent reply other threads:[~2024-01-30 3:05 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-29 13:01 [Bug target/113652] New: ppc: unrecognized opcode: `lfiwzx' csfore at posteo dot net 2024-01-29 13:07 ` [Bug target/113652] [14 regression] Failed bootstrap on ppc unrecognized opcode: `lfiwzx' with -mcpu=7450 rguenth at gcc dot gnu.org 2024-01-29 13:12 ` csfore at posteo dot net 2024-01-29 16:50 ` erhard_f at mailbox dot org 2024-01-29 17:51 ` csfore at posteo dot net 2024-01-29 20:49 ` csfore at posteo dot net 2024-01-30 3:05 ` linkw at gcc dot gnu.org [this message] 2024-01-30 3:26 ` linkw at gcc dot gnu.org 2024-01-30 3:44 ` pinskia at gcc dot gnu.org 2024-01-30 6:16 ` [Bug target/113652] " linkw at gcc dot gnu.org 2024-01-30 6:18 ` sjames at gcc dot gnu.org 2024-01-30 6:37 ` linkw at gcc dot gnu.org 2024-01-30 6:59 ` [Bug target/113652] [14 regression] " linkw at gcc dot gnu.org 2024-01-30 8:58 ` linkw at gcc dot gnu.org 2024-02-07 23:15 ` amodra at gmail dot com 2024-02-09 4:21 ` bergner at gcc dot gnu.org 2024-02-12 12:38 ` csfore at posteo dot net 2024-02-15 10:29 ` erhard_f at mailbox dot org 2024-03-27 13:46 ` rguenth at gcc dot gnu.org 2024-03-28 20:37 ` meissner at gcc dot gnu.org 2024-03-29 12:58 ` segher at gcc dot gnu.org 2024-03-29 13:04 ` segher at gcc dot gnu.org 2024-03-29 21:17 ` bergner at gcc dot gnu.org 2024-04-13 4:39 ` meissner at gcc dot gnu.org 2024-05-07 7:44 ` [Bug target/113652] [14/15 " rguenth at gcc dot gnu.org 2024-05-09 3:18 ` bergner at gcc dot gnu.org 2024-05-09 9:41 ` segher at gcc dot gnu.org 2024-05-09 13:55 ` erhard_f at mailbox dot 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-113652-4-VPyHk6d13j@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).