From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 73A163858CDA; Tue, 21 Nov 2023 10:29:38 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 73A163858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1700562578; bh=7j+bnohHoEiKh7cCY9WbjrG5qCgOvJ1noYij9Y/rXS0=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Pbyf0nTu9W2Z13g9IvvsNDwr3k9eVRdbrnTtQQg0S3ByRWMR5mi/d2UPYJHZpztzc M+LlhJUkaQOrby7RQTuSZRdpZTEmDWAMZkoEpjIPkPOBqojcclymMrWcpOz0/8VtbW s7f/WCBRopaGj+iqePk0psWx65UOD8baYc0H7oRc= From: "rdapp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112406] [14 Regression] Several SPECCPU 2017 benchmarks fail with on internal compiler error: in expand_insn, at optabs.cc:8305 after g:01c18f58d37865d5f3bbe93e666183b54ec608c7 Date: Tue, 21 Nov 2023 10:29:37 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rdapp at gcc dot gnu.org X-Bugzilla-Status: REOPENED X-Bugzilla-Resolution: 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=3D112406 --- Comment #18 from Robin Dapp --- Already in ifcvt we have: _ifc__60 =3D .COND_ADD (_2, _6, MADPictureC1_lsm.10_25, MADPictureC1_lsm.10= _25); which we should not. This is similar on riscv. But during value numbering it still is Value numbering stmt =3D _ifc__60 =3D .COND_ADD (_47, MADPictureC1_lsm.10_2= 5, _6, MADPictureC1_lsm.10_25); so we originally created the right thing. Hmm, no simplification is happening. Is there still a swap somewhere that should not be?=