public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67961] Incorrect type of meber of struct in error message
Date: Wed, 14 Oct 2015 14:26:00 -0000	[thread overview]
Message-ID: <bug-67961-4-nwC1BsErZx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67961-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to other+gcc from comment #0)
> where type of that rvalue variable is uint32_t not std::size_t.

There is no rvalue of type uint32_t. The type of the **lvalue** is uint32_t.

The rvalue is the temporary that gets created implicitly, which is of type
size_t.


FWIW clang doesn't mention rvalues, it just says there is no matching function
for the call because ...

prog.cc:4:6: note: candidate function not viable: no known conversion from
'std::uint32_t' (aka 'unsigned int') to 'std::size_t &' (aka 'unsigned long &')
for 1st argument


  parent reply	other threads:[~2015-10-14 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14  8:48 [Bug c++/67961] New: " other+gcc at meresinski dot eu
2015-10-14 14:14 ` [Bug c++/67961] " redi at gcc dot gnu.org
2015-10-14 14:26 ` redi at gcc dot gnu.org [this message]
2015-10-15  9:11 ` paolo.carlini at oracle dot com

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-67961-4-nwC1BsErZx@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).