From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6FAD73858413; Thu, 17 Mar 2022 18:49:41 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6FAD73858413 From: "andrew.cooper3 at citrix dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/104971] New: Optimisation for __builtin_ia32_readeflags corrupts the stack Date: Thu, 17 Mar 2022 18:49:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: andrew.cooper3 at citrix dot com X-Bugzilla-Status: UNCONFIRMED 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: 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: Thu, 17 Mar 2022 18:49:41 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D104971 Bug ID: 104971 Summary: Optimisation for __builtin_ia32_readeflags corrupts the stack Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: andrew.cooper3 at citrix dot com Target Milestone: --- Full example: https://godbolt.org/z/xGq3c4Mnc Given: int broken(void) { int fl =3D __builtin_ia32_readeflags_u64(); } gcc -O2 generates: broken: pushfq ret Which is going explode very quickly. Code generation appears to be safe without optimisation, but even -O alone = is enough to create problems. At a guess, the optimiser has concluded that the result is unused, drops the `pop %reg`, but fails to also drop the `pushf` too. Looking through history on Godbolt, it appears that GCC 4.9 (which introduc= ed this builtin) has correct optimised code generation, and it regressed betwe= en 4.9 and 5.1.=