public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/89237] Partial specialization incorrectly marked as ambiguous with sizeof(T) narrowing down to bool Date: Tue, 23 Jan 2024 20:25:18 +0000 [thread overview] Message-ID: <bug-89237-4-VwcnMe454K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-89237-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89237 Jason Merrill <jason at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org --- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> --- Created attachment 57198 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57198&action=edit WIP Some WIP for this PR. But looking through IMPLICIT_CONV_EXPR unconditionally breaks some testcases, and I don't want to spend any more time on this non-regression in stage 4.
prev parent reply other threads:[~2024-01-23 20:25 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-89237-4@http.gcc.gnu.org/bugzilla/> 2021-12-14 3:32 ` [Bug c++/89237] Partial specialization incorrectly marked as ambiguous pinskia at gcc dot gnu.org 2021-12-14 4:15 ` pinskia at gcc dot gnu.org 2024-01-23 20:25 ` jason at gcc dot gnu.org [this message]
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-89237-4-VwcnMe454K@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).