This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Removing -frwitable-strings
- From: espie at quatramaran dot ens dot fr (Marc Espie)
- To: gcc at gcc dot gnu dot org
- Cc:
- Date: Tue, 23 Dec 2003 14:31:30 +0100 (CET)
- Subject: Re: Removing -frwitable-strings
- Organization:
- References: <1071628676.3793.52.camel@minax.codesourcery.com>
In article <C134EE50-30DD-11D8-8C55-003065A77310@apple.com> you write:
>On Tuesday, December 16, 2003, at 06:37 PM, Mark Mitchell wrote:
>> So, here is a final chance: Does anyone object to the plan of (a)
>> deprecating -fwritable-strings in GCC 3.3.3 and (b) removing it in GCC
>> 3.4? If so, why?
>
>Well, a quick count has it breaking 20 of around 2039 software projects
>around here.
I believe we should first deprecate the feature, and give heavy hints in
the deprecation messages (using -Wwrite-strings -Wcast-qual).
I tried that on rogue. I just spent one hour making it const-correct.
Fortunately, some people had already cleaned up the code quite a bit.
Contrarily to a previous assertion, the previous security fixes have NOT
made rogue immune to writable strings. There was still one left in
throw.c's rand_around...
20 packages translates to over 20 hours of rather boring work. Or
possibly very hard work, as some of this code will probably never having
been cleaned up since its inception.