From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 71C2E3858407; Wed, 10 Jan 2024 08:12:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 71C2E3858407 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704874330; bh=C6YMhtM/dKIJzf9g8soRtY2zmcc4IVIZB1zrQeSoeH4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=mDW3dXJlDor8EccJWMej265roRyzok67I28SzlVVWMGyO8UUmokCUp6I35CJVS5Hh 4aZX9SSGlXFrUWyq5xy/D3urOZ8pKwimTAFIbKNa890NVIVWcxCDwDiBBJiboGSIxI RcokZSW5XA6TcBwGtcIeeG1QFhzeyLkcHROLJ0IY= From: "linkw at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: linkw at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113115 --- Comment #7 from Kewen Lin --- (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 pa= tch > 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=3Dpower9 (or later) is wrong= , and > should > not work. Using -mno-power9-vector is just weird. >=20 > If we can neuter the -mpower9-vector (etc.) options now, that would be go= od. > 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 test= ing.=