On 28/10/2007, Chris Quenelle <[EMAIL PROTECTED]> wrote:
> Shawn Walker wrote:
> > I've been trying to figure out how to activate the gnu_compat flag
> > that ube apparently supports via cc -Wu,<option here>.
>
> We've only started adding serious gcc compatibility features to the
> Sun compilers in the last release We still have a ways to go.  If you can
> identify specific features that we should add it will help us get those
> features fully implemented in a stable and documented way for
> the next release.

I appreciate that.

> We make features into wizard options for good reasons, they are
> untested, or known to have major problems.

I don't mind that as long as they're listed somewhere with the usual
interface stability warnings Sun graciously provides. i.e. if
something is labeled "Volatile" I know better than to come crying when
it breaks into a million pieces.

> By the way, people inside Sun have just as much trouble using
> undocumented features as people outside Sun.  ;-} There's really
> no special advantage to being inside Sun as far as this
> subject goes.

Except apparently they can be disclosed things I can't :(

> One reason the compiler team adds wizard options is to work around
> special, obscure problems for important customers.  One
> of these important customers in the Solaris team.
> Sometimes the changes are made at the last minute before a
> release, or in a patch.  So that's a perfect reason to
> leave them undocumented and turned off by default.
>
> tools-compilers is also a good way to follow up on compiler
> specific issues.

So what do I do when a Sun engineer says that they know of a wizard
option that will let me compile something with the public release of
Sun Studio but they can't give it to me?

Should I refer them to you?

-- 
Shawn Walker, Software and Systems Analyst
[EMAIL PROTECTED] - http://binarycrusader.blogspot.com/

"Beware of bugs in the above code; I have only proved it correct, not
tried it. " --Donald Knuth
_______________________________________________
tools-discuss mailing list
[email protected]

Reply via email to