From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 63C973858D33; Tue,  6 Feb 2024 10:00:49 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 63C973858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1707213649;
	bh=ixc/pnGtyM5e45S9HRrGhPyYqOu5vP9rbdNsdrV2lNM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=PwqdFDb35mh5cElPUOInKbQEyk8YG/DYpAzRzg48gW7LuYM3FFl/dXlcEYZHdILlz
	 AgrRxdmfzhpABmtSoJWGNEclRzDsG9WOP9iDHIWS7B2/4IpZ+qdExtQbZhiFOlaK6p
	 BRagzyso+RX8DXNYRvrxgxZViXGoxu3eg03/ifVU=
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/113359] [13 Regression] LTO miscompilation of ceph on
 aarch64
Date: Tue, 06 Feb 2024 10:00:48 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 13.2.1
X-Bugzilla-Keywords: lto, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
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: 13.3
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-113359-4-rRzjxsc3Qh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-113359-4@http.gcc.gnu.org/bugzilla/>
References: <bug-113359-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D113359

--- Comment #11 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
If there are two ODR types with same ODR name one with integer and other wi=
th
pointer types third field, then indeed we should get ODR warning and give u=
p on
handling them as ODR types for type merging.

So dumping their assembler names would be useful starting point.

Of course if you have two ODR types of different names but you mix them up =
in
COMDAT function of same name, then the warning will not trigger, so this mi=
ght
be some missing type compatibility check in ipa-sra or ipa-prop summary, to=
o.=