From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 3DDFC3857C5E; Tue, 29 Jun 2021 17:11:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 3DDFC3857C5E From: "amacleod at redhat dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/101254] [12 Regression] gcc head does not comply fully to -fwrapv since r12-1723 Date: Tue, 29 Jun 2021 17:11:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: amacleod at redhat 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: 12.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jun 2021 17:11:15 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D101254 Andrew Macleod changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #51083|0 |1 is obsolete| | --- Comment #9 from Andrew Macleod --- Created attachment 51084 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D51084&action=3Dedit another patch OK, fleshed it out. Your observations about [0,max] for unsigned are true,= but it was harmless. however, when I broke it into 3 cases, unsigned, wrapping signed and nornmal signed, it looks like I can simply treat it as wrapping = and non-wrapping.. since ~[0,0]for unsigned is the same as [1, max] anyway I added the LT, LE, and NE cases as well. I think this is now right and complete? or have I missed something else.. certainly possible,I'm developing a headache thinking about it.=