|
|
flag-day: reversion to Studio 10 compiler
Date: Sat, 12 Aug 2006 17:50:36 -0700
From: Danek Duvall <danek.duvall at sun dot com>
To: on-all at sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: flag-day: reversion to Studio 10 compiler
The switch to Studio 11 (Venus) resulted in the discovery of
6454083 SunStudio 11 compiler may generate incorrect assembly when used with -xO2 and -xarch=v9[ab ]
which caused
6453635 px should not call px_fm_attach before internal initialization
which prevents Fire platforms (Boston, Seattle, Chicago) from booting.
There may also be other subtle and unnoticed side effects which have not
yet been discovered (the extent of 6453635 hadn't been discovered in nearly
two weeks of PIT nightly testing and months of testing prior to
integration).
The fix to 6454083 is imminent as a new patch to Studio 11, but will not
arrive in time to apply to the CBE with any level of confidence before
buidl 46 needs to be delivered to RE. In addition, other consolidations
have discovered a small handful of other compiler bugs that will need to be
fixed, and because revving the compiler patch-level in the CBE is not
something to be undertaken lightly, we will be waiting for all these issues
to be fixed before switching back to Studio 11.
In the meantime, I have backed out
6311077 Enabling ON compilation with Sun Studio 11 (Venus)
and will be delivering build 46 with this respun into it. (Alas, an
intervening putback means that build 46 will diverge from the mainline;
anyone taking a child of the build 46 snapshot once it opens should take
this into account.)
Gatelings should be careful when using Studio 11 with this backed out. If
you use the standard SUNWonbld but don't change SPRO_VROOT in your env
file, then you will either use Studio 11 with the ON changes to make that
somewhat stable (as you presumably have been doing for the past two weeks)
or you will use Studio 10 without those changes, which involves compiler
flags Studio 10 doesn't understand.
The new tools will be available in /ws/onnv-tools before midnight tonight,
Pacific time. In the meantime, you can use nightly -t to get around any
problems.
If you have any questions or problems, please send us email at gk at onnv dot eng.
Thanks, and apologies for any inconvenience or confusion,
Danek
|