This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Removing -frwitable-strings

From: Paul Koning <pkoning at equallogic dot com>
To: jamie at shareable dot org
Cc: Joe dot Buck at synopsys dot COM, mark at codesourcery dot com, mrs at apple dot com, gcc at gcc dot gnu dot org, kcook34 at ford dot com, zack at codesourcery dot com, rearnsha at arm dot com
Date: Thu, 18 Dec 2003 16:20:35 -0500
Subject: Re: Removing -frwitable-strings
References: <908E76BD-3112-11D8-8C55-003065A77310@apple.com><1071722293.3579.107.camel@minax.codesourcery.com><20031218104828.A20777@synopsys.com><20031218185751.GF16315@mail.shareable.org>

>>>>> "Jamie" == Jamie Lokier <jamie@shareable.org> writes:

 Jamie> Someone said that -fwritable-strings could be implemented in
 Jamie> the front end, but currently it isn't and that adds unwanted
 Jamie> code to the back end.

 Jamie> Perhaps it's quite a simple change to make string constants
 Jamie> have type "char[]" in the C and C++ front ends instead of
 Jamie> "const char[]"?  (No, I'm not volunteering).

Isn't that already there?  -fno-const-strings (at least for C++).

I wonder if it would make sense to remove that, too, especially since
it's already marked as deprecated in the docs.

The docs clearly say that this does NOT make your strings writeable.

     paul

References:
- Re: Removing -frwitable-strings
  - From: Mike Stump
- Re: Removing -frwitable-strings
  - From: Mark Mitchell
- Re: Removing -frwitable-strings
  - From: Joe Buck
- Re: Removing -frwitable-strings
  - From: Jamie Lokier

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]