public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109751] boost iterator_interface fails concept check starting in gcc-13
Date: Fri, 05 May 2023 19:00:17 +0000 [thread overview]
Message-ID: <bug-109751-4-8dsqRT3dao@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109751-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109751
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Luke Dalessandro from comment #8)
>
> Right.
>
> I was sort of surprised that that boost code could get away with a requires
> on any of those CRTP functions where it uses the CRTP "D" type, but I tested
> gcc-12 and all the clangs, and nvc++, and msvc 19, and gcc-13 was the only
> one reporting problems here, so I went with consensus.
Note I could be wrong too. Which is why I kept it open until someone else who
is more familar with the C++ standard makes a judgement.
next prev parent reply other threads:[~2023-05-05 19:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 17:45 [Bug libstdc++/109751] New: boost interface_interface " ldalessandro at gmail dot com
2023-05-05 17:50 ` [Bug c++/109751] boost iterator_interface " pinskia at gcc dot gnu.org
2023-05-05 17:59 ` ldalessandro at gmail dot com
2023-05-05 18:06 ` ldalessandro at gmail dot com
2023-05-05 18:09 ` pinskia at gcc dot gnu.org
2023-05-05 18:11 ` ldalessandro at gmail dot com
2023-05-05 18:14 ` pinskia at gcc dot gnu.org
2023-05-05 18:41 ` pinskia at gcc dot gnu.org
2023-05-05 18:54 ` ldalessandro at gmail dot com
2023-05-05 19:00 ` pinskia at gcc dot gnu.org [this message]
2023-05-05 19:24 ` pinskia at gcc dot gnu.org
2023-05-05 20:01 ` pinskia at gcc dot gnu.org
2023-05-05 20:02 ` pinskia at gcc dot gnu.org
2023-05-06 22:02 ` redi at gcc dot gnu.org
2023-05-06 22:05 ` redi at gcc dot gnu.org
2023-05-06 23:28 ` ldalessandro at gmail dot com
2023-05-08 15:46 ` ldalessandro at gmail dot com
2023-05-08 16:00 ` redi at gcc dot gnu.org
2023-05-09 19:20 ` ppalka at gcc dot gnu.org
2023-05-09 21:24 ` [Bug c++/109751] [13/14 Regression] " ppalka at gcc dot gnu.org
2023-05-09 21:27 ` ppalka at gcc dot gnu.org
2023-05-10 19:10 ` ppalka at gcc dot gnu.org
2023-07-21 14:09 ` ppalka at gcc dot gnu.org
2023-07-27 9:26 ` rguenth at gcc dot gnu.org
2023-08-17 15:52 ` jason at gcc dot gnu.org
2023-08-22 18:36 ` cvs-commit at gcc dot gnu.org
2023-08-31 22:40 ` cvs-commit at gcc dot gnu.org
2023-08-31 22:40 ` jason at gcc dot gnu.org
2023-10-16 18:33 ` 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-109751-4-8dsqRT3dao@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).