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/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6 Date: Wed, 10 Jan 2024 08:12:09 +0000 [thread overview] Message-ID: <bug-113115-4-Hce91zAxck@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113115-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113115 --- Comment #7 from Kewen Lin <linkw at gcc dot gnu.org> --- (In reply to Peter Bergner from comment #5) > I really dislike the -mpower{8,9}-vector options, but maybe it's too late to > remove them for this release? I'm not sure how involved/invasive that patch > would be. Segher, do you have a preference on remove them now or use the > workaround above and remove in the next release? (In reply to Segher Boessenkool from comment #6) > Using -mpower9-vector while not having -mcpu=power9 (or later) is wrong, and > should > not work. Using -mno-power9-vector is just weird. > > If we can neuter the -mpower9-vector (etc.) options now, that would be good. > But > there are some complications with the testsuite at least? OK, it sounds that it's still acceptable to adjust this at this time point, so I'm working on a patch to evaluate its impact, will post it after full testing.
prev parent reply other threads:[~2024-01-10 8:12 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-22 14:13 [Bug target/113115] New: ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler fkastl at suse dot cz 2024-01-03 12:33 ` [Bug target/113115] " mjires at suse dot cz 2024-01-03 21:44 ` [Bug target/113115] [14 Regression] ICE In extract_constrain_insn_cached recog.cc with ppc64le-linux-gnu crosscompiler from r14-3592-g9ea1248604d7b6 pinskia at gcc dot gnu.org 2024-01-08 13:57 ` rguenth at gcc dot gnu.org 2024-01-08 20:50 ` bergner at gcc dot gnu.org 2024-01-09 2:07 ` linkw at gcc dot gnu.org 2024-01-09 5:08 ` bergner at gcc dot gnu.org 2024-01-09 7:54 ` segher at gcc dot gnu.org 2024-01-10 8:12 ` linkw at gcc dot gnu.org [this message]
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-113115-4-Hce91zAxck@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).