From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A640F3857C40; Wed, 14 Sep 2022 17:39:28 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A640F3857C40 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663177168; bh=zsbJ6DpwA8gmigha/1Ios15sXJ181UEyfSWhqHSXLN0=; h=From:To:Subject:Date:From; b=vPgAjPYapR2DJxzIss0kPuTeGcgUfPSnWXoZUYIgCjgcY915e2rRLYJzA1pEGTSjA Pv+Fc4H6w2I024YbTI5IRKzFryPNu0O1xfX3dhiBfjoi9bY4GkpCZ8PQkDzXM9wn7n 0xNO9c9YH7VlGkymo0m2DQz41pD9vK/Qm7EVZr4M= From: "immoloism at googlemail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106943] New: GCC building clang/llvm with LTO flags causes ICE in clang Date: Wed, 14 Sep 2022 17:39:28 +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: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: immoloism at googlemail 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 attachments.created 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=3D106943 Bug ID: 106943 Summary: GCC building clang/llvm with LTO flags causes ICE in clang Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: immoloism at googlemail dot com Target Milestone: --- Created attachment 53574 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D53574&action=3Dedit ICE error I've found an interesting ICE which only occurs when LTO flags are turned o= n in GCC while building clang and llvm while compiling compiler-rt-sanitizers. I= f I rebuild clang/llvm without the flto cflags then the bug does not appear. CFLAGS used to build clang/llvm "-march=3Dnative -O2 -pipe -fgraphite-ident= ity -floop-nest-optimize -flto=3D8 -fuse-linker-plugin -falign-functions=3D32" This is the first time I've run into anything like this so please ask if any other files or tests will help you identify the cause and I'd be happy to oblige. I have reported this to the LLVM team and they believe this could be an iss= ue your end so hopefully you have some ideas to add.=