From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6372F3AA11C2; Tue, 4 Jun 2024 17:11:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6372F3AA11C2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1717521067; bh=cOkHgLEzzUh8Z9Sj6XXYATIEzKWguR8jJfJqibcSrnA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=v6E3WF4Sb6nTUmAJdtgALiC1iB5YnbV02x7xCqOARSjXKsNQFlWZ6vxaT/OuqEa42 Lr8bYbc+b7jK5EzLzaSGfYaQu5bfMPhepqCTP9SHzbz30Kw7Vz2l3e6+8EC20U0Q4I 7EhP9q7NhvFsNPsFT/nJhXGFmQ2tz+b/Qxe05qy0= 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 17:11:07 +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 #10 from Djordje Baljozovic --- (In reply to Jakub Jelinek from comment #8) > Also, if building with GCC 11 works and with GCC 12 doesn't, can you build > two trees, one with either compiler and then bisect first among the shared > libraries or binaries (find out which shared library or binary is affecte= d), > among the static libraries (GCC 11 and 12 ought to be ABI compatible, so = try > linking some *.a libraries from one build and other from another build, > among the object files (start with linking half of the objects built by o= ne > compiler and another half by another compiler and depending on if it works > as expected or not change the set of objects to link). > If you get to one object file which when compiled with GCC 11 works even > when everything else has been compiled with GCC 12 or vice versa, you can > then try different options on that one (e.g. the -fno-strict-aliasing And= rew > mentioned, -O0 etc.), and/or > bisect inside of the source using #pragma GCC optimize(0) etc. > Anyway, if there is a single translation unit like that and ideally if you > find out which function is problematic, trying to stub functions it calls > and add a caller which calls that single function with the right arguments > turns it into a self-contained reproducer. Good idea(s). Let me try all Andrew's options firstly, and get back to you. Thanks, George=