From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7D4913840C05; Thu, 21 Apr 2022 09:25:27 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7D4913840C05 From: "guojiufu at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105297] [12 Regression] new modules 'xtreme' test cases FAILs Date: Thu, 21 Apr 2022 09:25:27 +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.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: guojiufu at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ppalka at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Apr 2022 09:25:27 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D105297 Jiu Fu Guo changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |guojiufu at gcc dot gnu.org --- Comment #11 from Jiu Fu Guo --- (In reply to Patrick Palka from comment #10) >=20 > Interestingly that doesn't seem to make a difference. What seems to matt= er > is whether the constexpr function modifies the CONSTRUCTOR that it return= s: >=20 > constexpr auto foo() { > struct S { int d; } t =3D {}; > t.d =3D 0; // doesn't ICE if this line is commented out > return t; > } >=20 > template > int bar() { > constexpr auto t =3D foo(); > return 0; > } Right, it is weird. Some PRs on Xtreme-* failure (including ICE) were also reported before. e.g. PR100052, PR101853, PR99910. As commented in those P= Rs, these may be random failures, and changes in headers that could expose the = ICE. I'm also wondering if this may be an issue hidden inside somewhere (GC?).=