This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/59939] No warning on signedness changes caused by implicit conversion
- From: "su at cs dot ucdavis.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 25 Jan 2014 19:06:34 +0000
- Subject: [Bug c/59939] No warning on signedness changes caused by implicit conversion
- Auto-submitted: auto-generated
- References: <bug-59939-4 at http dot gcc dot gnu dot org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59939
--- Comment #9 from Zhendong Su <su at cs dot ucdavis.edu> ---
(In reply to Marc Glisse from comment #8)
> I think Andrew's point is that we might have:
> ...
Thanks for your explanation Marc. I think I see the point now, although the
rational still feels a bit convoluted.
> As with many things, it is a matter of taste whether you want to ignore
> warnings in obviously dead code.
Yes, I very much agree --- many times it's purely a design decision.
But please allow me to argue the following point. Since "fn1(a,b)" is obviously
dead code in the originally reported test (because of which the two conversions
weren't warned), the dead code should then be warned, correct?