public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dangelog at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/96416] to_address() is broken by static_assert in pointer_traits Date: Wed, 21 Apr 2021 08:45:51 +0000 [thread overview] Message-ID: <bug-96416-4-lXsV0yESDC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96416-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96416 --- Comment #18 from Giuseppe D'Angelo <dangelog at gmail dot com> --- Hello, (In reply to Jonathan Wakely from comment #17) > (In reply to Giuseppe D'Angelo from comment #14) > > To summarize: > > > > * should a wording defect be raised against std::to_address(Ptr), to state > > that pointer_traits<Ptr> being well-formed is actually a prerequisite? > > I'd prefer if pointer_traits was just SFINAE friendly. I guess that's a reasonable thing to wish for, given I'm not the first falling for it; I hope I'll be the last :) > > * should LWG3446's resolution be amended? > > See https://cplusplus.github.io/LWG/issue3541 > > > * if there's going to be a GCC 10.3, is the commit above solving LWG3446 > > going to be cherry-picked into it? Otherwise, either one blacklists GCC 10, > > or has to specialize pointer_traits there as a workaround (?). > > It missed the 10.3 release, but it's on the gcc-10 branch as r10-9698, which > will be in GCC 10.4: > https://gcc.gnu.org/g:32a859531e854382c18abf0b14a306d83f793eb5 > That also includes the fix for LWG 3541. Thank you very much for the new issue and the cherry-pick of the fix.
next prev parent reply other threads:[~2021-04-21 8:45 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-02 4:17 [Bug libstdc++/96416] New: address_of() " whatwasthataddress at gmail dot com 2020-08-03 12:58 ` [Bug libstdc++/96416] " redi at gcc dot gnu.org 2020-08-03 15:34 ` whatwasthataddress at gmail dot com 2020-08-03 15:38 ` redi at gcc dot gnu.org 2020-11-11 17:46 ` redi at gcc dot gnu.org 2020-11-11 18:52 ` redi at gcc dot gnu.org 2020-11-11 19:10 ` redi at gcc dot gnu.org 2020-11-11 20:05 ` glenjofe at gmail dot com 2020-11-11 20:40 ` redi at gcc dot gnu.org 2020-11-11 20:41 ` redi at gcc dot gnu.org 2021-03-26 14:19 ` dangelog at gmail dot com 2021-03-26 14:45 ` dangelog at gmail dot com 2021-03-26 23:44 ` glenjofe at gmail dot com 2021-03-27 0:48 ` [Bug libstdc++/96416] to_address() " redi at gcc dot gnu.org 2021-03-27 1:41 ` arthur.j.odwyer at gmail dot com 2021-03-27 16:53 ` dangelog at gmail dot com 2021-03-27 19:46 ` redi at gcc dot gnu.org 2021-03-29 3:08 ` glenjofe at gmail dot com 2021-04-20 20:11 ` redi at gcc dot gnu.org 2021-04-21 8:45 ` dangelog at gmail dot com [this message] 2021-08-05 22:55 ` gcc-bugs at marehr dot dialup.fu-berlin.de 2021-09-28 14:00 ` [Bug libstdc++/96416] [DR 3545] " redi at gcc dot gnu.org 2021-11-25 23:12 ` cvs-commit at gcc dot gnu.org 2021-11-26 17:46 ` cvs-commit at gcc dot gnu.org 2021-11-26 17:52 ` redi at gcc dot gnu.org 2021-12-09 1:24 ` whatwasthataddress at gmail dot com 2022-06-28 10:41 ` jakub at gcc dot gnu.org 2023-07-07 9:00 ` rguenth 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-96416-4-lXsV0yESDC@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).