On Tue, 20 Mar 2007, Roland Mainz wrote:
[EMAIL PROTECTED] wrote:
On Tue, 6 Mar 2007, Roland Mainz wrote:
Garrett D'Amore wrote:
[snip]
IMO the problem needs to be handled from two sides:
1. Make the default setting for Sun Studio 12 "-xstrconst" and add an
option "-xstrnoconst" for backwards-compatibilty (CC:'ing
[EMAIL PROTECTED] for that). THIS IS VERY IMPORTANT to get the
"switch" done ASAP (see below)
2. Crawl over the OS/Net sources and add "-xstrconst" to the matching
Makefiles (the "compile OS/Net with gcc"-project already did lots of
work&&testing in this area which means the risk should be quite low)
[1] should make sure that future projects do not have to set explicitly
"-xstrconst" for each bit they compile (most projects from the "open
source" world treat string lierals as read-only anyway since this is the
default since gcc2.x and gcc4.x no longer has an option to make string
literals writeable). IMO this is the most important part since it should
elimitate the issue from userspace applications once Sun Studio 12 gets
used. The current default setting to treat string lierals is IMO not
good since it affects both memory usage and performance of applications
very badly
[2] should elimitate the problem from the OS/Net codebase and prepares
the tree for the upcoming "switch" in Sun Studio 12
[snip]
BTW, the RFE to make -xstrconst the default in C compiler exists for years.
It is CR 5011504. I've just made it externally visible -- should appear
on bugs.sun.com in 24 hours.
What about the idea to add a "-xstrnoconst" option to make string
literals writeable on demand ? Should I file a seperate RFE for that ?
The idea is already there.
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) [EMAIL PROTECTED]
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 7950090
(;O/ \/ \O;)
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
