From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9D95C3858C54; Fri, 12 May 2023 14:00:19 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9D95C3858C54 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1683900019; bh=yhBeauYzR/uGM0aAHifxP8yeTn2OyWjahBEYbWhgh4I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gagOpjxv/zIDqtI40qsgxOTZmoY/khwo+9fQiwiOWJWw1k4/5VEy9F/NYZyCvJqHx mNa6umZWLkzfDmTAELnUDqHGqiSJcuRK7bFlZJb8pXw9FzvhKMhRIP4VbQZM3u4uru fQxKgY18YdQfh7TnQa7l2wfAWscHmJdcOkbFnBnU= 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 14:00:19 +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 #12 from Alexander Monakov --- That would not fix the problem, lifetime-dse affects code that creates 'cla= ss User' objects, not the implementation of its 'operator new' override. (also the linked bug says "MDNode has the same pattern and the same issues") Is there any need to over-engineer this like that? I would hope enabling -fno-lifetime-dse globally would not be controversial for LLVM, especially given the existing bug report and long-term use of -fno-strict-aliasing.=