public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rudick at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102804] template matching fails w/ false ambiguity on ternary expressions with enums class defined with unsigned typdef
Date: Mon, 18 Oct 2021 16:23:42 +0000	[thread overview]
Message-ID: <bug-102804-4-88knBynzo8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102804-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102804

--- Comment #5 from Todd Rudick <rudick at gmail dot com> ---
Richard, is there a way to represent the part of this that is a bug? 
Presumably accepting the construct but having it break template specialization
with an error that can be arbitrarily disconnected from the definition is not a
desired behavior. In the production code that I eventually isolated this from,
there is in fact no reference at all to the header that contained the enum.

Also, it seems likely that the compiler state is bad at that point (?), as the
error message indicates an 'unsigned int' ambiguity that doesn't actually
exist.

  parent reply	other threads:[~2021-10-18 16:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-17 22:09 [Bug c++/102804] New: template matching fails w/ false ambiguity on ternary expressions with enums rudick at gmail dot com
2021-10-17 22:18 ` [Bug c++/102804] template matching fails w/ false ambiguity on ternary expressions with enums class defined with unsigned int32_t pinskia at gcc dot gnu.org
2021-10-18  0:04 ` [Bug c++/102804] template matching fails w/ false ambiguity on ternary expressions with enums class defined with unsigned typdef redi at gcc dot gnu.org
2021-10-18  0:16 ` redi at gcc dot gnu.org
2021-10-18  6:51 ` rguenth at gcc dot gnu.org
2021-10-18 16:23 ` rudick at gmail dot com [this message]
2021-10-18 16:37 ` [Bug c++/102804] [9/10/11/12 Regression] template matching fails w/ false ambiguity on ternary expressions with enums class defined with unsigned typedef redi at gcc dot gnu.org
2021-10-18 16:43 ` redi at gcc dot gnu.org
2021-10-18 21:08 ` pinskia at gcc dot gnu.org
2021-11-05 13:56 ` rguenth at gcc dot gnu.org
2022-04-15  1:55 ` cvs-commit at gcc dot gnu.org
2022-05-27  9:46 ` [Bug c++/102804] [10/11 " rguenth at gcc dot gnu.org
2022-06-28 10:46 ` jakub at gcc dot gnu.org
2023-07-07 10:41 ` [Bug c++/102804] [11 " 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-102804-4-88knBynzo8@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).