public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at integrable-solutions dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13932] [3.3/3.4/3.5 regression] duplicate warning message for conversion Date: Fri, 30 Jan 2004 16:03:00 -0000 [thread overview] Message-ID: <20040130160354.22222.qmail@sources.redhat.com> (raw) In-Reply-To: <20040130144911.13932.bangerth@dealii.org> ------- Additional Comments From gdr at integrable-solutions dot net 2004-01-30 16:03 ------- Subject: Re: New: [3.3/3.4/3.5 regression] duplicate warning message for conversion "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> writes: | This little gem | ----------------- | int i = 1.; | ----------------- | yields | g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc | x.cc:1: warning: initialization to `int' from `double' | x.cc:1: warning: argument to `int' from `double' | which is not only duplicated, but also seems | a) grammatically wrong in the first line (shouldn't it be | "initialization OF 'int' from 'double'"?) | b) nonsensical in the second line: it's not an argument TO | a FUNCTION "int", it's the argument to the ASSIGNMENT | to int | | Highly bogus... Completely agreed. Even more so, I think the diagnostic should NOT be emitted when the compiler does know for sure that the target can accurately hold the initializer with no loss (which is the case here). Will look into this after 3.3.3 -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13932
next prev parent reply other threads:[~2004-01-30 16:03 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-30 14:49 [Bug c++/13932] New: " bangerth at dealii dot org 2004-01-30 14:49 ` [Bug c++/13932] " bangerth at dealii dot org 2004-01-30 16:03 ` gdr at integrable-solutions dot net [this message] 2004-01-30 17:23 ` pinskia at gcc dot gnu dot org 2004-02-05 5:20 ` cvs-commit at gcc dot gnu dot org 2004-02-05 5:22 ` cvs-commit at gcc dot gnu dot org 2004-02-05 5:23 ` [Bug c++/13932] [3.3 " mmitchel at gcc dot gnu dot org 2004-02-22 16:27 ` cvs-commit at gcc dot gnu dot org 2004-02-22 16:27 ` gdr at gcc dot gnu dot 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=20040130160354.22222.qmail@sources.redhat.com \ --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: linkBe 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).