From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1109F385840F; Fri, 3 Mar 2023 19:21:36 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1109F385840F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1677871297; bh=Ia4xyPXEoT762XaVJy6uZN/wNzodExBuuie78feYpXs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=wh3DT8dCGpYcOh6fFboMi94LBkYjhvWeVCZAH2HG5yFXPuuG6B2b70Z18IWxwB4eK +CBSF30MBi746plZ0seDrSHMrdjPYZM+8jE2qz5D0rnQtiNWh/ibzvub4BNXuXQBes Gu1/uS7JDymb5sva/StnkxHXCj6fmKtsk0BIlJec= From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/101118] coroutines: unexpected ODR warning for coroutine frame type in LTO builds Date: Fri, 03 Mar 2023 19:21:36 +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: 11.1.0 X-Bugzilla-Keywords: C++-coroutines, diagnostic, lto X-Bugzilla-Severity: normal X-Bugzilla-Who: iains 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: --- 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=3D101118 --- Comment #10 from Iain Sandoe --- Hmm... maybe I am being too hasty here. If the coroutine has a definition in a header, then the coroutine frame type _should_ be the same for each instance of it. So maybe this is actually reporting a genuine ODR violation?=