From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6DA7F3858404; Thu, 13 Oct 2022 22:12:43 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6DA7F3858404 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1665699163; bh=aYQm4TiLfGOeZt3bZfBR8O6KzPgQSlLbaSGIzjfOsDE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=EP2QT+XWpm6JZCwUsbZl+GI6c0kgsBBbLnMxt1f54nwtG4yZwYupuo9733ouX5kyv KfC0OxNvgQ+fzZ5AItSJpkoa8AhLo44nlFevbQ/Ej5ugcr6uS9UQvMHd18FSZuX89g rKopd8zj+rSEOMn3MxeTmCs2O/sm9I7Nf/bB0xBM= From: "segher at gcc dot gnu.org" 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: Thu, 13 Oct 2022 22:12:43 +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: segher at gcc dot gnu.org 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 #29 from Segher Boessenkool --- (In reply to Hongtao.liu from comment #23) > looking at i386.c put_condition_code used by *setcc_qi, it looks like (EQ > (reg:CCCmode FLAG_REG) (const_int 0)) means get carry flag. > Not (LTU: (REG:CCCmode FLAGS_REG) (const_int 0)). > Now I got more confused. (eq (reg:CCC 17) (const_int 0)) means that the comparison that did set reg= 17 returned "equal". CCCmode is just like CCmode, but *only* the carry flag is valid.=