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/113652] [14 regression] Failed bootstrap on ppc unrecognized opcode: `lfiwzx' with -mcpu=7450 Date: Fri, 29 Mar 2024 21:17:24 +0000 [thread overview] Message-ID: <bug-113652-4-l7X3If7qov@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 Peter Bergner <bergner at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #22 from Peter Bergner <bergner at gcc dot gnu.org> --- I kicked off a 7450 build on one of our BE system and I can confirm we hit this error. I also saw us generating the 2 operand form of the mfcr instruction which also leads to an assembler error because the 7450 doesn't support that either. Were we are in the build is compiling libgcc and the routines for handling KFmode values. The build machinery is explicitly adding -mvsx -mfloat128 to the compiler options when building those source files and that seems bogus to me, since the 7450 does not have VSX hardware. It's the explicit addition of the -mvsx option to the command line that is causing the lfiwzx and 2 operand mfcr instructions to be generated, not some internal mishandling of the -mcpu=7450 option. My $0.02 worth is we should be generating an error when trying to use -msx with -mcpu=7450 or any other cpu that doesn't have VSX hardware. I also don't think we should be building these KFmode files which require VSX when the underlying cpu we're targeting doesn't support it.
next prev parent reply other threads:[~2024-03-29 21:17 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 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 [this message] 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-l7X3If7qov@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).