public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60402] [DR 1395] const overload with variadics declared ambiguous according to standard
Date: Sat, 04 Dec 2021 07:35:05 +0000	[thread overview]
Message-ID: <bug-60402-4-uTw3SWUgWd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60402-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|SUSPENDED                   |NEW

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
[Moved to DR at the November, 2016 meeting.]

(In reply to Daniel Krügler from comment #2)
> No, this is not related to bug 58156. According to the current core language
> of C++11, the code is indeed ambiguous.
> 
> There exists currently a core language issue to fix that, see
> 
> http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_active.html#1395

Hmm, but this example is still rejected in both GCC and clang (and MSVC) but
accepted for ICC. The example in both defect reports is done correctly with GCC
and all.

      parent reply	other threads:[~2021-12-04  7:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-60402-4@http.gcc.gnu.org/bugzilla/>
2014-03-03 19:47 ` [Bug c++/60402] const overload with variadics declared ambiguous according to standard (may be related to bug 58156) nate.mcnamara at morganstanley dot com
2014-03-03 20:31 ` daniel.kruegler at googlemail dot com
2014-06-11 17:55 ` [Bug c++/60402] [Core/1395] const overload with variadics declared ambiguous according to standard paolo.carlini at oracle dot com
2021-12-04  7:35 ` pinskia 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-60402-4-uTw3SWUgWd@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).