This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/12963] Wrong and misleading warning encourages writing non-portable code
- From: "bagnara at cs dot unipr dot it" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Nov 2003 21:13:54 -0000
- Subject: [Bug c++/12963] Wrong and misleading warning encourages writing non-portable code
- References: <20031108134219.12963.bagnara@cs.unipr.it>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From bagnara at cs dot unipr dot it 2003-11-21 21:13 -------
(In reply to comment #4)
> Since GCC is warning based on the target you are using, I am closing as will
not fix.
In my opinion, this is a mistake: people wishing to write 100% portable code
should not be forced to switch all warnings off in order to get rid
of this useless warning (yes, useless, because there is nothing sensible the
sensible programmer can do about it).
Warnings such as this one should be issued only when specifically requested.
At the very least, it should be possible to selectively switch off this
kind of warnings.
But closing the bug report as you are doing (without even addressing my
question "why then there is no such a warning for void*, not even with
-W -Wall?") will not make the problem go away. The problem is there.
I don't think this anxiety to close bug reports before the issue has
been studied and discussed in depth is going to help.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12963