From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0CD683811081; Tue, 4 Jun 2024 18:43:24 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0CD683811081 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1717526605; bh=kIdarBIVo11myGhf8J2LI+ih2jFNswOFltPTu9+jZ70=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vFBXvF4HdYmb1DvfvWrnhXjTq/fH/0bt+APELYw7Vg3om/FaEU/b6kHRK1F8g1D2p RSTsPB+tHWBadcMKwDrrhirev95jVyRhT+TtbRkImdAB6FxLDij5cpZnB004YfwcvB jHdru18FajYpk3NtNelB1FG2XwolzEbxoz/6NiZc= From: "djordje.baljozovic at ac dot rwth-aachen.de" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/115345] [12/13/14/15 Regression] Different outputs compared to GCC 11- and MSVC/Clang Date: Tue, 04 Jun 2024 18:43:24 +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: 12.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: djordje.baljozovic at ac dot rwth-aachen.de X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D115345 --- Comment #11 from Djordje Baljozovic --- (In reply to Djordje Baljozovic from comment #9) > (In reply to Andrew Pinski from comment #7) > > A few questions, does `-fsanitize=3Dundefined -fsanitize=3Daddress` rep= ort > > anything? Does it work at -O0 and not just -O3? Does adding > > -fno-strict-aliasing to the command line "fix" the crash? Are there any > > warnings with `-Wextra -Wall` that might be causing an issue? >=20 > Have not tested -O0 and -fno-strict-aliasing; will let you know if this > fixed the problem. > No warnings with -Wextra -Wall to my knowledge. >=20 > Sincerely, > George Hi Andrew and Jakub, The results are more than interesting: 1. -fno-strict-aliasing: none of the inputs processed (with O3) 2. O0: all but one input processed 3. O3: none of the inputs processed 4. O1 and O2: all inputs processed without any issues -- this did it. Now the question is: how on Earth did O1/O2 do the trick, and not O0?! Once again, thanks a lot for your detailed and quick responses. George P.S. I will keep @Jakub's bisect idea in mind if something like this happen= s in the future.=