From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9024D3856968; Fri, 12 May 2023 15:48:14 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9024D3856968 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683906494; bh=/pHBmZb4HHphgNQBk3iSK4ndqre9uz7PADCUb4OdXng=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eiKjd7PaZI/HLwwd8dcU4Zx5FGcC9cNHO27pVPaqygjtWCkv1dnNSErdROPAptSry rBgYG0ARGVdoV6aws8+3Gy1TzwtRh3SWd0nXpdlfnHZzFbVhfOqEdiDfY2jRMLHWtL BFeB/wkG/ooCjENiOsltANrwmFgUGz1b0u2eQZU4= From: "amonakov at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106943] GCC building clang/llvm with LTO flags causes ICE in clang Date: Fri, 12 May 2023 15:48:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: needs-reduction, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: amonakov at gcc dot gnu.org 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=3D106943 --- Comment #21 from Alexander Monakov --- (In reply to Xi Ruoyao from comment #18) > Maybe. Should we send a patch? Yes, if we have a volunteer. > If I read the LLVM code correctly, -fno-strict-aliasing is enabled for > Clang, but not other LLVM parts. Right, thanks for the correction.=