public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ldalessandro at gmail dot com" <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: Sat, 06 May 2023 23:28:37 +0000 [thread overview] Message-ID: <bug-109751-4-DmU5QQz2oe@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 #15 from Luke Dalessandro <ldalessandro at gmail dot com> --- Thanks for looking at this. I'd like to report it back to boost as an issue, but I want to make sure I understand what to tell them. 1. The error produce by Andrew's reduction ("error: satisfaction of atomic constraint ... depends on itself") is different than the one produced in the original code ("error: satisfaction value of atomic constraint ... changed) from 'false' to 'true'"). I'm to understand that this isn't important here, it's basically reacting to the same thing? 2. The fundamental problem with the boost code is the use of a constrained `friend` template that depends on the template parameter D, that is not yet complete when it is evaluated? 3. A fix for this issue in boost and the iterator_interface is to use a constrained member function rather than attempting to use a constrained friend function? Also, from what I understand, I should report Andrew's reduced case as a bug in clang, and msvc (and maybe nvc++ with its different front-end), which I will do. Thanks for looking into this.
next prev parent reply other threads:[~2023-05-06 23:28 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 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 [this message] 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-DmU5QQz2oe@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: linkBe 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).