public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53159] Missing narrowing check
Date: Fri, 11 Jul 2014 21:54:00 -0000	[thread overview]
Message-ID: <bug-53159-4-0qg0VujoAZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53159-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Fri Jul 11 21:53:59 2014
New Revision: 212469

URL: https://gcc.gnu.org/viewcvs?rev=212469&root=gcc&view=rev
Log:
/cp
2014-07-11  Paolo Carlini  <paolo.carlini@oracle.com>

    PR c++/53159
    * call.c (build_user_type_conversion_1): Copy LOOKUP_NO_NARROWING
    into convflags.
    * decl.c (check_initializer): Don't call check_narrowing here,
    set LOOKUP_NO_NARROWING.
    * typeck2.c (digest_init_r): Likewise.

/testsuite
2014-07-11  Paolo Carlini  <paolo.carlini@oracle.com>

    PR c++/53159
    * g++.dg/cpp0x/Wnarrowing1.C: New.

Added:
    trunk/gcc/testsuite/g++.dg/cpp0x/Wnarrowing1.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/call.c
    trunk/gcc/cp/decl.c
    trunk/gcc/cp/typeck2.c
    trunk/gcc/testsuite/ChangeLog


  parent reply	other threads:[~2014-07-11 21:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-29 14:00 [Bug c++/53159] New: " marc.glisse at normalesup dot org
2012-05-21 17:47 ` [Bug c++/53159] " paolo.carlini at oracle dot com
2012-05-21 20:55 ` paolo.carlini at oracle dot com
2012-05-21 23:44 ` paolo.carlini at oracle dot com
2013-03-22 14:43 ` jakub at gcc dot gnu.org
2013-03-22 18:17 ` paolo.carlini at oracle dot com
2013-03-24 18:15 ` paolo.carlini at oracle dot com
2014-04-22 11:35 ` jakub at gcc dot gnu.org
2014-07-11 21:54 ` paolo at gcc dot gnu.org [this message]
2014-07-11 21:55 ` 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-53159-4-0qg0VujoAZ@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).