This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Platform: x86 (Solaris and Linux) Scenario: - Create C/C++ project - Call context menu on project and select Properties menu item - Set Build|C++ Compiler|Development Mode = Performance Release ==> check options (for example press "..." button in "Additional Options" field) NetBeans 6.9beta (SunStudio, SunStudio12.1 or OracleSolarisStudio toolchain): -fast -xipo -xvector=simd -g0 Latest builds: SunStudio or OracleSolarisStudio: -fast -xipo -g0 SunStudio12.1: -fast -xipo -xvector=simd -g0
Logic of tool collection manager for creating Oracle Solaris Studio is: - manager detect latest Oracle Solaris Studio by following priority: 1. SunStudio_12.2 - Oracle Solaris Studio 12.2 Compiler Collection 2. SunStudioExpressAten - Oracle Solaris Studio Express 6/10 Compiler Collection 3. SunStudio_12.1 - Sun Studio 12.1 Compiler Collection 4. SunStudioExpressCeres - Sun Studio Express Compiler Collection (Ceres) 5. SunStudio_12 - Sun Studio 12 Compiler Collection 6. SunStudio_11 - Sun Studio 11 Compiler Collection 7. SunStudio_10 - Sun Studio 10 Compiler Collection 8. SunStudio_9 - Sun Studio 9 Compiler Collection 9. SunStudio_8 - Sun Studio 8 Compiler Collection latest studio has appropriate name and flavor. - manger creates two link on latest studio compilers: 1. SunStudio - Sun Studio Compiler Collection 2. OracleSolarisStudio - Oracle Solaris Studio Compiler Collection both link have own flavor that is a common flavor of all studios (equals SunStudio_8). I.e. SunStudio has flavor SunStudio and OracleSolarisStudio has flavor OracleSolarisStudio. Is it bug?
I think it is at least confusing. If user does not have anything older than 12.1 why to keep the set of option that is compatible with older versions? I think correct logic should be to pick common set of flags for installed toolchains only.
I do not understand that is "common set of flags". Explain please. For example: Let exist two tool collections and tools has following flag set: - S1 for C tool from first tool collection - S2 for C tool from second tool collection Common set of flags is: - intersection of S1 and s2 - set from oldest tool - or anything else?
Intersection sounds most right. However if OracleSolarisStudio is an alias, then it might make sense to just pick the flags from the toolchain that it refers to.
i.e., restore behavior that was in beta: - manger creates two link on latest studio compilers: 1. SunStudio - Sun Studio Compiler Collection 2. OracleSolarisStudio - Oracle Solaris Studio Compiler Collection both links have flavor that is a flavor of the latest studio.
Yep. I think it is more intuitive for users and exactly what Valery is asking for.
fixed, change set: http://hg.netbeans.org/cnd-main/rev/892958204b2d
Integrated into 'main-golden', will be available in build *201005192201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/892958204b2d User: Alexander Simon <alexvsimon@netbeans.org> Log: fixed BZ#186350 SunStudio and OracleSolarisStudio compiler options (Performance Release mode) are changed in latest builds (1-2 week ago)
QA: please evaluate issue as show stopper according to NetBeans 6.9 High Resistance procedure.
it's difference in behavior of IDE comparing with beta. Fix is safe and correct. And if you think that the current behavior is not needed, but behavior of Beta is needed => I agree with fix.
Accepted as a show stopper after discussion. Starting show stopper process.
verified in dev cnd build from bertram. please push to release69 clone.
Fix transplanted to release69 as 34acd9a8c7e5
verified in RC1