From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D07303858C2B; Wed, 25 Jan 2023 16:47:40 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D07303858C2B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674665260; bh=Ofq/DDUIqrmUsZFORZ/00j961zLkp8iq+Obc75/kv5c=; h=From:To:Subject:Date:In-Reply-To:References:From; b=V42ogR37StHofr5IGKUtlPbET3YnrHQzEnVCwAULz72roUszGbpqLCVBbLOVA6TTu txaLMbOVcSAZaS/Ya1LvZxIp6GXvpu+fz3Y3tT3mpsThFgXL4ObO0sqY7v/13QdP67 IMfSqMEyNBbqIKJIPCE5Xn7DpKroh6uYvnb5Uy5w= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: =?UTF-8?B?W0J1ZyBjKysvODc1MTJdIEVycm9yOiB0aGUgdHlwZSDigJhjb25z?= =?UTF-8?B?dCBhdXRv4oCZIG9mIOKAmGNvbnN0ZXhwcuKAmSB2YXJpYWJsZSBpcyBub3Qg?= =?UTF-8?B?bGl0ZXJhbA==?= Date: Wed, 25 Jan 2023 16:47:40 +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: 8.2.0 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: mpolacek 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=3D87512 --- Comment #6 from Andrew Pinski --- (In reply to Guo Youtao from comment #5) > This bug can still be triggered in gcc-11 and gcc-12. That is unrelated bug. Most likely an issue with pointer to member functions which is might have some known issues too.=