This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/61579] -Wwrite-strings does not behave as a warning option
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 21 Jun 2014 15:45:07 +0000
- Subject: [Bug c/61579] -Wwrite-strings does not behave as a warning option
- Auto-submitted: auto-generated
- References: <bug-61579-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61579
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jsm28 at gcc dot gnu.org,
| |manu at gcc dot gnu.org
--- Comment #1 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> ---
Agreed. It seems that in order to get the desired warning, the solution was to
change the type and warn implicitly, rather than detect the potential cases
explicitly. This is a quite ugly hack.
On the other hand, I don't expect an existing GCC developer to fix this, given
the long history of -Wwrite-strings. Someone new will have to step up,
implement it and defend it in front of the C FE maintainers.