From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 83A31385828C; Tue, 18 Oct 2022 00:19:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 83A31385828C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666052383; bh=rDdgV2D2dTnma4wTL3gVubzzYCUkdoY/y6x78owv0fA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=FFf4OkYlgTpkmn8vP8ZDd4nf0UpsECF2ENDXeyrdkFK8dMDFqF+n57mfI0WTVPKSb xtpSpXiepHTStjDuI3xTtITnDWtuguxleZA1MWSzaCcZY6zr9jTsTeZ/5ggI/sc/cv QO09CI+MS7iRN6MzoB4xU81eNmCw/bnOaCHQXteA= From: "hjl.tools at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/107172] [13 Regression] wrong code with "-O1 -ftree-vrp" on x86_64-linux-gnu since r13-1268-g8c99e307b20c502e Date: Tue, 18 Oct 2022 00:19:41 +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: 13.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: hjl.tools at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.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=3D107172 --- Comment #39 from H.J. Lu --- (In reply to Segher Boessenkool from comment #38) > You cannot put a const_int in a MODE_CC. It is meaningless. Reg 17 in (insn 49 10 50 2 (parallel [ (set (reg:CCC 17 flags) (ne:CCC (reg:SI 82 [ a.1_2 ]) (const_int 0 [0]))) (set (reg:SI 92) (neg:SI (reg:SI 82 [ a.1_2 ]))) ]) "107172.c":4:10 680 {*negsi_ccc_1} becomes const_int 1 since a.1_2 is known non-zero. Roger's patch simplifies const_int in a MODE_CC properly.=