From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D75F2384AB41; Thu, 18 Apr 2024 11:57:18 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D75F2384AB41 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1713441438; bh=Jk52Oa3ltArdd7XOwWGnLCfFfnY7hbf8v2QnfeUvGt8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Cz4sgyGG5Qlrw7dQnpX/TLm5tpdDAUL5uwI0ngz8VaiwovzUnbwpNt8wpBf3wCUfN IgePRGBm+SuDclMWL2mhO17sgeM0WENwmxD6w96ou46Rb6SsLsYhQWvgMICTtbQMR6 rP/x8fLfZZLdpimuIOwDbpOGQKC9MvVypjJxpXTM= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug lto/114574] [14 regression] ICE when building curl with LTO (fld_incomplete_type_of, at ipa-free-lang-data.cc:257) since r14-9763 Date: Thu, 18 Apr 2024 11:57:14 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: lto X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: lto X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 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=3D114574 --- Comment #29 from Jakub Jelinek --- (In reply to uecker from comment #28) > I do not fully understand yet what happens for may_alias, but it if we la= ter > complete the struct with the may_alias attribute it seems we would also n= eed > to update the previously created pointer so that it has > TYPE_REF_CAN_ALIAS_ALL. Setting TYPE_STRUCTURAL_EQUALITY for incomplete > structs also for pre-C23 seems to fix the assertion failure, but I am not > sure if this fixes the underlying bug. Certainly that may_alias case isn't specific to just C, C++ behaves the sam= e, and I'd just say don't do that, you can always put the may_alias attribute = on the forward declaration of the struct if all pointers to it are supposed to alias.=