public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marc.glisse at normalesup dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/50011] [C++0x] warning: narrowing conversion of 'i' from 'short unsigned int' to 'int' inside { } [-Wnarrowing]
Date: Mon, 08 Aug 2011 11:14:00 -0000	[thread overview]
Message-ID: <bug-50011-4-cItdlyvwHy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50011-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Marc Glisse <marc.glisse at normalesup dot org> 2011-08-08 11:14:06 UTC ---
(In reply to comment #5)
> It gives a warning probably because of a mistake in the gcc sources.

Or not. In your example, remove short and replace int with long. Now you are
asking for a warning that would be there on x86 but not on x86_64, that doesn't
help write portable code.

Now your suggestion may be right, but I want to stress that it is not obvious.


  parent reply	other threads:[~2011-08-08 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-07 11:10 [Bug c++/50011] New: " zsojka at seznam dot cz
2011-08-07 20:46 ` [Bug c++/50011] " marc.glisse at normalesup dot org
2011-08-08  7:55 ` zsojka at seznam dot cz
2011-08-08 10:08 ` rguenth at gcc dot gnu.org
2011-08-08 10:13 ` marc.glisse at normalesup dot org
2011-08-08 11:04 ` zsojka at seznam dot cz
2011-08-08 11:14 ` marc.glisse at normalesup dot org [this message]
2011-08-08 14:37 ` jason at gcc dot gnu.org
2011-08-08 18:09 ` jason 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-50011-4-cItdlyvwHy@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).