public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "f.b.brokken at rug dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/100288] [11/12 Regression] g++-11 internal error and fails to precompile a concept
Date: Sat, 01 May 2021 20:31:32 +0000 [thread overview]
Message-ID: <bug-100288-4-yaureAAIQf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100288-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100288
--- Comment #4 from Frank B. Brokken <f.b.brokken at rug dot nl> ---
Dear ppalka at gcc dot gnu.org, you wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100288
>
> Patrick Palka <ppalka at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Keywords| |ice-on-invalid-code
> See Also| |https://gcc.gnu.org/bugzill
> | |a/show_bug.cgi?id=99599
>
> --- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> ---
> Agreed, the testcase looks invalid much like PR99599. One workaround for
> avoiding the constraint recursion here would be to change the signature of
>
> template <OstreamInsertable Type>
> inline void operator<<(CSVTabIns &&tab, Type const &value)
>
> to something like
>
> template <std::same_as<std::remove_cvref_t<CSVTabIns>> U, OstreamInsertable
> Type>
> inline void operator<<(U &&tab, Type const &value)
>
> so that the constraint OstreamInsertable<Type> is checked on this overload only
> if the first argument to << has the expected type.
>
> --
> You are receiving this mail because:
> You reported the bug.
Hi Patrick,
Thanks for your e-mail.
Since (AFAICS) you directly and only sent your e-mail to me I'm wondering
whether you want me to comment on your e-mail. It's getting kind of late here,
but I could send a more extensive reply tomorrow. Let me know if that's what
you want.
I tried your suggestion, and it seems to solve the issue. But at the same time
it puzzles me why
template <OstreamInsertable Type>
inline void operator<<(CSVTabIns &&tab, Type const &value)
{}
won't be instantiated for FMT in
inline void operator<<(CSVTabIns &tab, FMT::FMTHline hline)
{
tab << (*hline)(1); // insert hline in the next column
}
when FMT defines FMTHline as 'typedef FMT (*FMTHline)(unsigned)' and
std::ostream &operator<<(std::ostream &out, FMT const &fmt)
is declared. I would have expected that
tab << (*hline)(1); // insert hline in the next column
would cause the compiler to instantiate
template <OstreamInsertable Type>
inline void operator<<(CSVTabIns &&tab, Type const &value)
{}
for Type = FMT.
Maybe I'm missing something here? And it's also not something that caused the
compiler's internal error.
next prev parent reply other threads:[~2021-05-01 20:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 10:54 [Bug c++/100288] New: " f.b.brokken at rug dot nl
2021-04-28 21:29 ` [Bug c++/100288] [11/12 Regression] " mpolacek at gcc dot gnu.org
2021-04-28 22:03 ` mpolacek at gcc dot gnu.org
2021-04-29 16:13 ` ppalka at gcc dot gnu.org
2021-05-01 18:22 ` ppalka at gcc dot gnu.org
2021-05-01 20:31 ` f.b.brokken at rug dot nl [this message]
2021-05-03 14:01 ` ppalka at gcc dot gnu.org
2021-07-28 7:06 ` rguenth at gcc dot gnu.org
2021-08-17 20:16 ` ppalka at gcc dot gnu.org
2021-11-05 14:01 ` ppalka at gcc dot gnu.org
2022-01-21 12:17 ` rguenth at gcc dot gnu.org
2022-04-21 7:49 ` rguenth at gcc dot gnu.org
2022-05-11 15:03 ` [Bug c++/100288] [11/12/13 " ppalka at gcc dot gnu.org
2022-05-11 15:04 ` ppalka at gcc dot gnu.org
2022-09-09 22:22 ` ppalka at gcc dot gnu.org
2023-03-16 18:23 ` cvs-commit at gcc dot gnu.org
2023-03-16 18:26 ` ppalka 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-100288-4-yaureAAIQf@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).