public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.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 13:13:46 +0000 [thread overview]
Message-ID: <bug-105297-4-n3EslCL6s5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105297-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105297
--- Comment #13 from Patrick Palka <ppalka at gcc dot gnu.org> ---
(In reply to Jiu Fu Guo from comment #11)
> (In reply to Patrick Palka from comment #10)
> >
> > Interestingly that doesn't seem to make a difference. What seems to matter
> > is whether the constexpr function modifies the CONSTRUCTOR that it returns:
> >
> > constexpr auto foo() {
> > struct S { int d; } t = {};
> > t.d = 0; // doesn't ICE if this line is commented out
> > return t;
> > }
> >
> > template<int>
> > int bar() {
> > constexpr auto t = 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
> PRs, 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?).
In this case I suspect it's just a bug in the modules code, I opened PR105322
to track it.
next prev parent reply other threads:[~2022-04-21 13:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 20:21 [Bug c++/105297] New: " iains at gcc dot gnu.org
2022-04-16 20:22 ` [Bug c++/105297] " iains at gcc dot gnu.org
2022-04-20 13:53 ` jakub at gcc dot gnu.org
2022-04-20 13:59 ` jakub at gcc dot gnu.org
2022-04-20 14:23 ` jakub at gcc dot gnu.org
2022-04-20 14:29 ` jakub at gcc dot gnu.org
2022-04-20 14:31 ` hp at gcc dot gnu.org
2022-04-20 16:01 ` redi at gcc dot gnu.org
2022-04-20 16:14 ` ppalka at gcc dot gnu.org
2022-04-20 16:18 ` ppalka at gcc dot gnu.org
2022-04-20 17:17 ` jakub at gcc dot gnu.org
2022-04-20 17:59 ` ppalka at gcc dot gnu.org
2022-04-21 9:25 ` guojiufu at gcc dot gnu.org
2022-04-21 12:35 ` cvs-commit at gcc dot gnu.org
2022-04-21 13:13 ` ppalka at gcc dot gnu.org [this message]
2022-04-21 13:14 ` ppalka at gcc dot gnu.org
2022-04-22 5:53 ` guojiufu at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-105297-4-n3EslCL6s5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).