public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105394] [12 Regression] ICE: verify_gimple failed with MVE during GIMPLE pass: veclower2 Date: Tue, 26 Apr 2022 12:40:25 +0000 [thread overview] Message-ID: <bug-105394-4-kA8mHmLz95@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105394-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105394 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org Ever confirmed|0 |1 Last reconfirmed| |2022-04-26 Status|UNCONFIRMED |ASSIGNED --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, in my cross-arm build I get > ./cc1plus -quiet t.c -I include -march=armv8.1-m.main+mve -mfloat-abi=hard -O cc1plus: error: target CPU does not support ARM mode while in my cross-aarch64 build: > ./cc1plus -quiet t.c -I include -march=armv8.1-m.main+mve -mfloat-abi=hard -O cc1plus: error: unrecognized command-line option '-mfloat-abi=hard' cc1plus: error: unknown value 'armv8.1-m.main+mve' for '-march' cc1plus: note: valid arguments are: armv8-a armv8.1-a armv8.2-a armv8.3-a armv8.4-a armv8.5-a armv8.6-a armv8.7-a armv8.8-a armv8-r armv9-a in the cross-arm build adding -mthumb reproduces the ICE, I guess my configury (--target=arm-none-linux-gnueabihf --with-float=hard --with-cpu=cortex-a9 --with-fpu=neon-fp16) plays a role here. I will have a look.
next prev parent reply other threads:[~2022-04-26 12:40 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 12:23 [Bug tree-optimization/105394] New: " acoplan at gcc dot gnu.org 2022-04-26 12:40 ` rguenth at gcc dot gnu.org [this message] 2022-04-26 12:42 ` [Bug tree-optimization/105394] " acoplan at gcc dot gnu.org 2022-04-26 13:18 ` rguenth at gcc dot gnu.org 2022-04-26 13:19 ` rguenth at gcc dot gnu.org 2022-04-26 13:22 ` [Bug target/105394] " rguenth at gcc dot gnu.org 2022-04-29 9:07 ` [Bug target/105394] [12/13 " rguenth at gcc dot gnu.org 2022-04-29 9:20 ` rguenth at gcc dot gnu.org 2022-04-29 9:57 ` rguenth at gcc dot gnu.org 2022-04-29 9:59 ` acoplan at gcc dot gnu.org 2022-05-03 8:34 ` acoplan at gcc dot gnu.org 2022-05-03 8:49 ` rguenther at suse dot de 2022-05-03 9:19 ` cvs-commit at gcc dot gnu.org 2022-05-03 9:25 ` [Bug target/105394] [12 " rguenth at gcc dot gnu.org 2022-05-06 8:33 ` jakub at gcc dot gnu.org 2022-05-06 9:27 ` cvs-commit at gcc dot gnu.org 2022-05-06 9:28 ` rguenth 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-105394-4-kA8mHmLz95@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).