public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102804] [9/10/11/12 Regression] template matching fails w/ false ambiguity on ternary expressions with enums class defined with unsigned typedef
Date: Fri, 15 Apr 2022 01:55:37 +0000	[thread overview]
Message-ID: <bug-102804-4-oUGpl5S1MS@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 #8 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:

https://gcc.gnu.org/g:e580f81d22d61153564959f08d9a6d3bcc7fd386

commit r12-8173-ge580f81d22d61153564959f08d9a6d3bcc7fd386
Author: Jason Merrill <jason@redhat.com>
Date:   Thu Apr 14 17:49:47 2022 -0400

    c++: unsigned int32_t enum promotion [PR102804]

    There's been an extension for a long time to allow applying 'unsigned' to
an
    int typedef, but that was confusing the integer promotion code.  Fixed by
    forgetting about the typedef in that case.

    I'm going to make this an unconditional pedwarn in stage 1.

            PR c++/102804

    gcc/cp/ChangeLog:

            * decl.cc (grokdeclarator): Drop typedef used with 'unsigned'.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/unsigned-typedef1.C: New test.

  parent reply	other threads:[~2022-04-15  1:55 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
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 [this message]
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-oUGpl5S1MS@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).