public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/42356] confused compiler
Date: Sat, 22 Oct 2011 12:27:00 -0000	[thread overview]
Message-ID: <bug-42356-4-44zvV5YzkX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-42356-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42356

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2011-10-22
                 CC|                            |manu at gcc dot gnu.org
     Ever Confirmed|0                           |1

--- Comment #7 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2011-10-22 12:27:11 UTC ---
Clang prints:

/tmp/webcompile/_26276_0.cc:17:19: error: no matching member function for call
to 'newNode'
    bar*    b = f.newNode<bar>();
                ~~^~~~~~~~~~~~
/tmp/webcompile/_26276_0.cc:6:13: note: candidate function template not viable:
requires 1 argument, but 0 were provided
    T*      newNode(U u) { return newNode()->init(u); }
            ^
/tmp/webcompile/_26276_0.cc:6:13: note: candidate function template not viable:
requires 1 argument, but 0 were provided
/tmp/webcompile/_26276_0.cc:8:13: note: candidate function template not viable:
requires 2 arguments, but 0 were provided
    T*      newNode(U u, V v) { return newNode()->init(u, v); }
            ^
/tmp/webcompile/_26276_0.cc:8:13: note: candidate function template not viable:
requires 2 arguments, but 0 were provided

which is nicer except for the duplicated messages.

The first thing that should go away is the "expected primary-expression" stuff.


  parent reply	other threads:[~2011-10-22 12:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-42356-4@http.gcc.gnu.org/bugzilla/>
2011-09-28 21:28 ` paolo.carlini at oracle dot com
2011-10-22 12:27 ` manu at gcc dot gnu.org [this message]
2011-10-22 12:29 ` [Bug c++/42356] improve list of candidates and error recovery for ambiguous call manu at gcc dot gnu.org
2011-10-22 13:01 ` redi at gcc dot gnu.org
2011-10-22 13:08 ` redi at gcc dot gnu.org
2011-10-22 13:21 ` redi at gcc dot gnu.org
2011-10-22 13:30 ` manu at gcc dot gnu.org
2011-10-22 15:53 ` igodard at pacbell dot net
2011-10-22 19:43 ` redi at gcc dot gnu.org
2011-10-23  0:46 ` manu at gcc dot gnu.org
2011-10-23  0:47 ` manu at gcc dot gnu.org
2011-10-23  1:29 ` igodard at pacbell dot net
2011-10-23  1:55 ` redi at gcc dot gnu.org
2011-10-23  2:04 ` redi at gcc dot gnu.org
2021-09-07 18:21 ` pinskia at gcc dot gnu.org
2009-12-12  7:39 [Bug c++/42356] New: confused compiler igodard at pacbell dot net
2009-12-12  9:48 ` [Bug c++/42356] " paolo dot carlini at oracle dot com
2009-12-14  4:51 ` igodard at pacbell dot net
2009-12-14  8:45 ` paolo dot carlini at oracle dot com
2009-12-14  9:27 ` paolo dot carlini at oracle dot com
2009-12-14 14:58 ` igodard at pacbell dot net

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-42356-4-44zvV5YzkX@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).