From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 91FEA3858CDA; Tue, 24 Oct 2023 17:45:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 91FEA3858CDA DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1698169546; bh=TSxS2z/FU3Y1+NnKRCT21yeoWHwG4EOQDpF6jCvXgSU=; h=From:To:Subject:Date:From; b=gm4CGDzdf+6C3mXTaIbmArcvpLvCZQHP/srdH3w4MwNV6DHlg8Gx4CSS+23T81QuG 4Y8vdRtFt91i7SHIEBOniY/Yn8WGB10PbN2VK+RXZX0gPfeszD0bTDDU0MUzT5tsON WH+rpyBUKBL/wUIuURej78uK+VchVWtq3hq6ECv8= From: "kloczko.tomasz at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/111964] New: 13.2.1: potential GIMPLE bug in inline assempler Date: Tue, 24 Oct 2023 17:45:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: kloczko.tomasz at gmail 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D111964 Bug ID: 111964 Summary: 13.2.1: potential GIMPLE bug in inline assempler Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: kloczko.tomasz at gmail dot com Target Milestone: --- According to node developers it is bug in GIMPLE and inline assembler causi= ng that node build with enabled LTO fails with missing PushAllRegistersAndIterateStack symbol. More details about how to build nodejs 21.0.0 to reproduce this issue is on https://github.com/nodejs/node/issues/50347=