Contents
1. Sun Studio Express - March 2009 Build
2. System and Hardware Requirements
3. Installing This Sun Studio Express Build
4. New and Changed Features Since Sun Studio 12 Release
5. Update Notification
6. Third-Party Technology
7. Features That Have Been Removed in This Release
8. Usage Tracking Enabled
1. Sun Studio Express -- March 2009 Build
Welcome to the Sun Studio Express Program. The Sun Studio Express 3/09
release is the official build used for the
Sun Studio 12 Update 1 Early
Access Program.
Support for this release is available if you install it on the
OpenSolaris operating system. To download
OpenSolaris 2008.11, see the Get OpenSolaris page. For information on
support options, contact your Sun Sales Representative. For instructions on
installing the Sun Studio Express 3/09 package from the OpenSolaris developer
repository, see Installing on the OpenSolaris OS.
We look forward to your feedback.
Join the
»Sun Studio Forums to get answers
to your questions from our engineers as well as the community,
and to leave feedback about what what worked and what didn't, and what we should improve.
The
»Sun Studio 12 Documentation Center
links to all the manuals, man pages, and readmes for the Sun Studio 12 software release,
on which this express build is based. The new features added since the Sun
Studio 12 software release are listed in the New and Changed
Features section of this readme.
Additional information about this express build can be found on the
»Express wiki pages.
If you cannot find the information you need through these sources, use the
»Sun Studio Forums to get
assistance.
2. System and Hardware Requirements
The minimum system and hardware requirements for this Sun Studio
Express build are:
Hardware
- Minimum on SPARC: Sun Ultra 60 (450 MHz, UltraSPARC II processor)
- Minimum on x86/x64: Pentium III 500-MHz or any AMD64 Opteron or Athlon
- Memory: Recommended 1 to 2 GBytes
- Swap: 1 Gbyte
- Disk space:
- SPARC platforms: 1.4 GBytes
- x86 platforms: 782 MBytes
- Linux platforms: 658 MBytes
Operating Systems
- Solaris versions:
- Solaris 10 01/06 or later update
- OpenSolaris 2008.11
- Linux versions:
- SuSE Linux Enterprise Server 10
- Red Hat Enterprise Linux 5
- Ubuntu 8.04 and 8.10
- CentOS 5
If you want to try Sun Studio Express on a Solaris Express build, or on any Linux distribution that
minimally has the 2.6.X Linux kernel and 2.4+ glibc, please give us
feedback on your experience in this environment through the
»Sun Studio Forums.
Note: The Sun Studio package installer, IDE, and Performance Analyzer
require Java SE Development Kit (JDK) 6 Update 3 or higher, which can be downloaded from the
»Java SE Downloads site
if the required version is not available on your target platform.
3. Installing This Sun Studio Express Build
This Sun Studio Express release is available as a package installer and as
a tarfile installer. (Additional installer options are described in the
»Express Details wiki pages.)
You do not need to have root access to run the tarfile installer; the
package installer requires root access.
If you installed the Sun Studio Express 11/08 release, you must uninstall that
release, using the uninstall.sh script in the installation directory (for
example, /opt/SUNWspro), before installing the Sun Studio Express 3/09
release.
The default installation directory for Sun Studio Express 3/09 on Solaris
platforms is /opt/SSX0903 (for Sun Studio Express 11/08, the default
installation directory was /opt/SUNWspro). On Linux platforms, the default installation directory
is/opt/sun/sunstudioceres (same as for Sun Studio Express 11/08).
This Sun Studio Express release is also available in the OpenSolaris
development repository for installation on the OpenSolaris OS. For instructions on
installing the Sun Studio Express 3/09 from the repository, see Installing on the OpenSolaris OS.
Installing Using the Package Installer
You can run the package installer in two modes: graphical user interface
(GUI) mode or non-GUI mode. The GUI mode lets you select which components
of the Sun Studio software to install and lets you specify an installation directory
different than the default installation directory. The non-GUI mode
installs all components of the Sun Studio software in the default installation
directory.
To install the Sun Studio Express release using the package installer:
- Download the package installer for your platform from the
»Sun Studio Express page into
a scratch download directory such as
/var/tmp. Make the installer
executable by typing the following command:
$ chmod +x ./installer_name
- Become superuser (root):
$ su
Password: root-password
- Start the installer:
- To start the installer in GUI mode, type the following and perform steps 4
through 9 when the installer GUI has started up.
# sh ./installer_name
- To start the installer in command-line mode, type the following:
# sh ./installer_name --silent
The installer proceeds
with installation, and the prompt returns when installation is complete.
- On the License agreement page, review the license agreement, select the
acceptance checkbox, and click Next.
- On the Sun Studio Installer page, if you want to choose which Sun Studio
compilers and tools to install:
- Click Customize.
- In the Customize Installation dialog box, click the appropriate checkbox to
deselect any component you do not want to install.
- Click OK.
- Click Next.
- On the Sun Studio Installation page, accept the default installation
directory for the Sun Studio software or specify another directory. Click Next.
- On the Summary page, verify that the list of components to be installed is
correct and that you have adequate space on your system for the installation.
Click Install to begin the installation.
- When the installation is complete, click Finish to exit the installer.
Installing Using the Tarfile Installer
To install the Sun Studio Express release using the tarfile installer:
- Download the tarfile installer for your platform from the
»Sun Studio Express page into a scratch
DOWNLOAD-DIRECTORY such as
/var/tmp (for the OpenSolaris
OS, download the tar file installer for the Solaris OS on x86 platforms). Make
the installer executable by typing the following command:
$ chmod +x ./tarfile-installer-name
-
Install Sun Studio Express by running the installer in the directory where you want
the Express release to be installed:
$ cd installation_directory
$ sh download_directory/StudioExpress-OS-PLATFORM-DATE-ii.sh
--print-sla
$ sh download_directory/StudioExpress-OS-PLATFORM-DATE-ii.sh
--accept-sla
Do not attempt to install this Express release in a directory that already contains
a previous Sun Studio or Sun Studio Express release. The script will detect this and
issue an error message.
After Installing
After installation, the installer opens a web browser and asks you to use your
Sun Online Account to register your copy of
Sun Studio with the Sun Inventory.
Registration is not required, but it allows you to organize your products in the
Sun Inventory and receive timely information from Sun.
The installer also registers this copy of Sun Studio in your local Service Tags database (if this service is available).
»Read more about Sun Inventory and Service Tags.
Before using Sun Studio compilers and tools, you will need to update
your PATH and MANPATH environment variables to the installation and documentation directories or modify
your home directory's ..cshrc file (for C shell) or
.profile file (for Bourne or Korn shells) to make these changes permanent.
If you use csh:
% setenv PATH installation_directory/bin:$PATH
% setenv MANPATH installation_directory/man:$MANPATH
If you use sh, ksh, or bash:
% PATH=installation_directory/bin:$PATH; export PATH
% MANPATH=installation_directory/man:$MANPATH; export MANPATH
The Sun Studio Express 3/09 release is available for download and
installation as a single package in the Open Solaris development repository, and can be
installed on the OpenSolaris 2008.11 OS.
Package name : sunstudioexpress
Version: 0.2009.3
You can install the Sun Studio Express 3/09 using the Package Manager or
from the command line:
To install the Sun Studio Express 3/09 package using the Package
Manager:
- On your OpenSolaris desktop, click the Add More Software icon or choose
System > Administration > Package Manager.
- In the Package Manager, choose File > Manage Repositories. In the
Manage Repositories dialog box, type developer in Name field and
http://pkg.opensolaris.org/dev in the URL field. Click Add.
- After the
repository has been added to the list, click the Preferred radio button next to
it to make it the preferred repository. Click Close.
- The Package Manager refreshes its catalogs and loads information from the
repository you added. When it has finished these updates, type studio
in the Search field. In the Search results, click the checkbox to select
sunstudio, then click Install/Update.
To install the Sun Studio Express 3/09 package from the command line,
type:
$ pfexec pkg set-authority -P -O http://pkg.opensolaris.org/dev developer
$ pfexec pkg install sunstudioexpress
If you previously installed the Sun Studio Express 05/08 release or the
Sun Studio Express 11/08 release in your
OpenSolaris 2008.11 environment, it is uninstalled automatically before the Sun
Studio Express 3/09 release is installed.
After you have installed the Sun Studio Express 3/09 release, the Sun Studio
software is available in /usr/bin and the Sun Studio man pages are
available in /usr/man. If necessary, update your PATH
and MANPATH environment variables respectively to include these paths.
Testing Your Installation
Test your installation by launching the Sun Studio IDE. From a terminal command-line prompt, type:
% sunstudio
4. New and Changed Features
Here is an overview of some of the new features in this Express build of Sun
Studio compilers and tools. Note that most of these features might not be
documented in the Sun Studio man pages in this build.
Some of these features are experimental and might not be available in future
releases. Some of these features might change significantly in future releases.
The documentation is also preliminary and might not reflect the full range of
functionality or problems and workarounds.
You will find more detail on these features on the
»Express Details wiki pages.
Performance Analyzer
The Performance Analyzer introduces new features for analyzing OpenMP
programs:
- A new collector for OpenMP 3 profiling is available, but not enabled by default.
It can be enabled by setting the environment variable SP_COLLECTOR_NEWOMP,
and works only for code compiled with the option -qoption iropt
-Apcg:mfcxt. If you enable the new collector, the following features are
available:
- The Analyzer GUI includes OMP Parallel Regions tab and OpenMP Tasks tab, which are available when OpenMP
data is collected, and have entries for the source lines of each construct and
metrics for those entries.
- Support has been added in the experiment format for OpenMP 3.0 profiling.
- Two new commands for OpenMP profiles, OMP_preg and OMP_task have
been added.
- User mode presentation of OpenMP profiles has been changed so that the parallel
loop functions are no longer shown.
The Performance Analyzer introduces major enhancements for analyzing MPI programs:
- The collect command has a new -M on option that is used to collect data on MPI programs. The target program should be mpirun, from Sun HPC ClusterTools 8, although
mpirun from other Open MPI implementations might also work.
- The Analyzer GUI includes the following new features:
- Context menus have been added to the MPI Timeline, MPI Chart, Functions,
Callers-Callees, and Timeline tabs.
- Keyboard shortcuts have been added for navigation, selection, and zoom actions
in the MPI Timeline, MPI Chart, and Timeline tabs.
- Navigation buttons have been added to the toolbars in the MPI Timeline and
MPI Chart tabs.
- MPI Timeline tab, which shows a view of an MPI program's data over time. The MPI Timeline tab shows a set of bars, one for each MPI rank, indicating when each process is in user code and when it is in MPI code, and displaying messages sent among the processes.
- MPI Chart tab, which you can use to generate different displays of the data to analyze. The MPI Chart tab shows a variety of one- and two-dimensional plots of data and other aggregated data concerning MPI processing.
- Zooming and filtering capabilities to focus on particular aspects of the data in the MPI Timeline and MPI Chart tabs.
- With applications created using Sun HPC ClusterTools 8 Early Access 2,
clock-profiling MPI experiments show two new metrics, MPI Work Time and MPI Wait Time.
You can find details about how to use the new features in the Sun Studio Performance Analyzer for
MPI programs on the
»MPI Analyzer wiki page.
Additional Changes to the Performance Analyzer tools
- Changes to experiment format to support MPI experiments and to support
MPI Work and MPI Wait metrics from Sun HPC
ClusterTools 8 Early Access 2.
- Changes to the
collect command (in addition to MPI
changes):
- Hardware counter profiling on the Solaris OS accepts libcpc generic
counters, and where libcpc recognizes them, numeric values for counter
specifications.
- Hardware counter profling on the Linux OS accepts numeric values for counter
specifications.
- Hardware counter profiling is now supported for the Intel Nehalem processor.
- Hardware counter profiling is now supported
for the Intel Atom processor on the Solaris OS.
- The
-I and -N options are accepted when
-c (count) profiling is specified.
- The
-J option for Java profiling can support multiple
arguments to the JavaTM Virtual Machine (JVM) as a
quoted string containing blank or tab separated arguments. (The terms "Java
Virtual Machine" and "JVM" mean a Virtual Machine for the
Java platform.)
- Hardware counter profiling has better support for Intel Core2 and AMD
Family 10h processors.
- The
collector command in the dbx debugger has
better support for Intel Core2 and AMD Family 10h processors.
- Changes to the Performance Analyzer GUI (in addition to MPI and OpenMP changes):
- The Show/Hide dialog box now supports a third option, API-only.
- The
tabs directive in an .er.rc file now
specifies tab order as well as tab visibility.
- Changes to the
er_print command:
- If you enable the new collector for OpenMP profiling by setting the
SP_COLLECTOR_NEWOMP environment variable, the following new features are
available:
- User mode presentation of OpenMP profiles has been changed so that the parallel
loop functions are no longer shown.
- Two new commands for OpenMP profiles, OMP_preg and OMP_task have
been added.
- The
er_print command has been ported to run in 64 bits, and will run the 64-bit
version if the underlying system supports it, unless the
SP_COMMAND_64 environment variable is set.
- A new
object_api command enables API-only processing of call stacks
from the named objects.
- You can include the
object_show, object_hide,
and object_api commands in .er.rc files.
- A new
objects_default command resets the default for all
shared objects. You cannot include this command in .er.rc files.
- The
tabs directive in an .er.rc file now
specifies tab order as well as tab visibility.
-
With Sun HPC ClusterTools 8 Early Access 2, clock-profiling MPI experiments show two
new metrics, MPI Work Time and MPI Wait Time.
- Compiler commentary controls, the
cc, scc, and
doc commands, have been extended to all control over whether the
compiler options used to build the object are shown at the bottom of the
source display.
- Two APIs have been added to the Thread Analyzer:
tha_check_datarace_mem instructs the Thread Analyzer
to monitor or ignore accesses to a specified block of memory when doing
data race detection.
tha_check_datarace_thr instructs the Thread Analyzer to
monitor or ignore memory accesses by one or more specified threads when
doing data race detection.
IDE
The following features are carried over from
the November 2008 Express release:
- Based on NetBeans IDE 6.5
- The new Memory window displays the contents of memory addresses
currently used by the process being debugged.
- The new Call Graph window displays a tree view of either the
functions called from a selected function, or the functions that
call that function.
-
Syntactic and semantic errors are highlighted as you type code.
-
You can package completed applications as tar files, zip files,
SVR4 packages, RPMs, or Debian packages.
-
You can define remote hosts and use development tools on those hosts
to build and run projects from your client system.
The following are carried over from the July 2008 Express release:
- The Include Hierarchy window lets you inspect the hierarchy
of source and header files
- The Type Hierarchy window lets you inspect all
supertypes and subtypes of a class
- A new toolbar button lets you toggle between corresponding source and header files
- Code completion now works for
#include directives
- The new Go to Type menu item lets you find a type (class, struct, enum, or typedef)
by its name or prefix
- The new Go to Include menu item lets you go directly to a file that is included in
a source or header file
- The new Go to Function or Variable menu item lets you find a function or variable
by its name or prefix
- Project dependencies can be created for projects from existing code
- A choice of formatting styles for your source code
- The new Threads window shows you all the threads in the current debugging
session
- The new Disassembler window displays the assembly instructions for the current source
file
- The new Usages window shows you everywhere a class (structure), function,
variable, macro, or file is used in your project's source code
C, C++, and Fortran Compilers
-
Object files created by the compilers on the Solaris OS on x86 platforms or the
Linux OS are incompatible
with previous compiler versions if the application code contains functions with parameters or
return values using _m128/_m64 data types. Users with .il files,
assembler code,
or asm inline statements calling these functions also need to be aware of this
incompatibility.
- The -xprofile=collect and -xprofile=use options provide
inmproved support for profiling multi-threaded, dynamically linked applications.
- The
-xarch=ssse3 option adds the SSSE3 instruction set to
the SSE3 instruction set.
- The
-xarch=sse4_1 option compiles for the SSE4.1 ISA.
- The
-xarch=sse4_2 option compiles for the SSE4.2 ISA.
- The
-xarch=sparcima option compiles for the sparcima version
of the SPARC-V9 instruction set, plus the UltraSPARC extensions.
- The
-xchip=core2 option optimizes for the core2 processor.
- The
-xchip=sparc64vii option optimizes for the Fujitsu SPARC64® VII
processor.
- The
-xchip=penryn option optimizes for the Intel® Penryn
processor.
- The
-xchip=nehalem option optimizes for the
Intel® CoreTM (Nehalem) processor.
- The
-xchip=ultraT2plus option optimizes for the UltraSPARC® T2 Plus
processor.
- The
-xcrossfile=1 option becomes an alias of the
-xipo=1 option. The -xcrossfile=0 option no longer
has any effect. Specifically, -xcrossfile=1 and -xcrossfile=0 results in
-xipo=1.
- On Solaris platforms, the
-xpec[=yes|no] option generates a PEC binary that is
recompilable for use with the Automatic Tuning System (ATS).
- The
-xtarget=woodcrest option expands to -xarch=ssse3
-xchip=core2 -xcache=32/64/8:4096/64/16.
- The
-xtarget=sparc64vii option expands to
-xarch=sparcima -xchip=sparc=sparc64vii
-xcache=64/64/2:5120/256/10.
- The
-xtarget=penryn option expands to
-xarch=sse4_1 -xchip=penryn -xcache=32/64/8:6144/64/24.
- The
-xtarget=nehalem option expands to -xarch=sse4_2
-xchip=nehalem -xcache=32/64/8:256/64/8:8192/64/16.
- The
-xtarget=ultraT2plus option expands to -xarch=sparcvis2
-xcache=8/16/4:4096/64/16 -xchip=ultraT2plus.
- The
-Y option does not accept i as an argument.
- On SPARC® platforms, the
-xdepend option is now implicitly
enabled for optimization levels -x03 or higher, and is no longer
included in the expansion of the -fast option.
- Support for OpenMP 3.0 in this Express release includes a
libmtsk library. OpenMP programs will link with this library by
default instead of the libmtsk library in the Solaris OS.
-xannotate[=yes|no]
(SPARC platforms only) Instructs the compiler to create binaries that can
be transformed later by binary modification tools like binopt(1).
C Compiler
- The
-W option does not accept i as an argument.
- The
-xsb and -xsbfast options are obsolete and
have been removed.
- A new flag has been added to the
-xcheck option,
[no%]init_local.
-
__FUNCTION__ is a predefined identifier that contains the
name of the lexically-enclosing function. It is functionally equivalent to the
c99 predefined identifier, __func__. On Solaris platforms,
__FUNCTION__ is not available in -Xs
and -Xc modes.
- In standard C, a case label in a
switch statement can have
only one associated value. The Sun Studio C compiler allows an extension
found in some compilers known as case ranges.
- The second operand in a conditional expression can be omitted. If the first
operand is then non-zero, the value of the conditional expression is that of
the first operand.
- For the
-features=[no%]conststrings option, which
enables and disables string literal placement in read-only memory, the default is
-features=conststrings, which replaces the deprecated
-xstrconst option.
- The
-include filename option for specifying
preprocessor include files has been added.
- New behavior for the preprocessor
## operator: The compiler now issues a warning diagnostic for an undefined
## operation (C standard, section 3.4.3), where undefined is a
## result that, when preprocessed, consists of multiple tokens
rather than one single token (C standard, Section 6.10.3.3(3)). The result of
an undefined ## operation is now defined as the first individual
token generated by preprocessing the string created by concatenating the
## operands.
C++ Compiler
Fortran Compiler
- Quad precision (REAL*16) is implemented on x86 platforms.
REAL*16 is 128-bit IEEE floating point.
- New -ext_names=fsecond-underscore appends two underscores to external
names that contain an underscore, and a single underscore to those that do not.
This option is equivalent to gfortran's -fsecond-underscore option. Thi
soption does not affect external symbols with the BIND(C) attribute.
- New IVDEP directive and new compiler option -xivdep
- The
-Qoption option does not accept ube_ipa as
an argument.
- The
-xvpara option, which shows parallelization warning
messages, is now supported.
- The
-sb, -sbfast, -xsb
and -xsbfast options are obsolete and have been removed.
- The compiler normally creates temporary files in the
/tmp
directory. You can specify another directory by setting the
TMPDIR environment variable.
- The behavior of the
cpu_time() Fortran 95 intrinsic routine
is different between Solaris and Linux platforms.
- The Fortran 2003
IMPORT statement is implemented.
Compilers and Assemblers on x86 Platforms
- New MOVBE assembly instruction for Intel Atom processor
- New Intel AES assembly instructions
- SSSE3 Assembly syntax/semantic and corresponding compiler intrinsics
- SSE4.1 Assembly syntax/semantic and corresponding compiler intrinsics
(Rev 1.0)
- SSE4.2 Assembly syntax/semantic and corresponding compiler intrinsics
- Two new assembler options:
-C and -a32
-
The
-b option, which generates extra symbol table
information for the SourceBrowser, is now obsolete.
dbx Debugger
- Runtime checking (RTC) now gives information about array out-of-bounds
access on the Solaris OS on x86 platforms.
- Runtime Checking (RTC) now supports access, leaks, and memuse checking
on the following Linux platforms: SuSE Linux Enterprise Server 10, Red Hat Enterprise Linux 5.
- A new graphical user interface (GUI) for dbx, dbxtool, is included in this release.
For information on invoking dbxtool, see the dbxtool.1 man page. dbxtool is a
separate GUI from the Sun Studio IDE, but is also based on NetBeans IDE 6.5.
dbxtool provides access to all the functionality of dbx. It also supports attaching to a process as it starts executing to begin debugging it immediately (see the ss_attach.1 man page), and fixing and continuing, which lets you relink source files after you make changes, without recompiling the entire program.
- dbx can now evaluate function parameters and local variables in
optimized code when the code provides the needed debugging information.
For more information, see Optimized
Code Debugging With Sun Studio dbx
Sun Performance Library
OpenMP 3.0
Support for OpenMP 3.0 features in the
C, C++, and Fortran compilers:
libmtsk
library- Tasking
- Loop collapse
- Runtime routines for nesting support
- Runtime routines for runtime schedule
- Environment variables
OMP_STACKSIZE and
OMP_WAIT_POLICY
- AUTO loop schedule
- Enhanced threadprivate support in C++
- Threadprivate static class member (C++)
- Unsigned int loop control variable (C and C++)
- New value for
_OPENMP macro (200805L)
Added in the November 2008 Express Release:
- f90 allocatable arrays
- C++ iterator loops
- C++ pointer loops
For more detail on these features, see the
»Express Details wiki pages.
DLight
DLight offers a variety
of instrumentation that takes advantage of the Solaris
TM Dynamic Tracing (DTrace)
debugging and performance analysis functionality. In this Express release,
DLight is supported on Linux platforms for two instruments: Clock Profiler
(based on Performance Analyzer) and Java Ticker. For more information, see the
DLight
Tutorial.
DTrace GUI Plugin
The NetBeansTM DTrace GUI Plugin is a graphical user
interface (GUI) for
running DTrace scripts.
The DTrace GUI includes Chime,
a graphical tool for visualizing DTrace aggregations. For information on using
the DTrace GUI, see NetBeans DTrace GUI
Plug-in.
5. Update Notification
The Update Notification feature periodically checks www.sun.com and communicates
available changes related to your Sun Studio software, including patches and major
software updates. In this Sun Studio Express build, only usage information is communicated. This
information is used by Sun Microsystems to improve future Sun Studio software
releases. This information is anonymous and cannot be associated to any individual or
organization.
To disable Update Notification, set the SUNW_NO_UPDATE_NOTIFY environment
variable to any value other than false.
6. Third-Party Technology
Third-Party Licenses
Sun Studio Express 3/09 software includes third-party technologies governed
by the
Sun
Studio Express 3/09 third-party license readme file, the
NetBeans 6.5
third-party license readme file, and the
NetBeans
Dynamic Tracing (DTrace) GUI Plugin third-party license readme file.
Source Code for libelf,ld, and
perfctr
Source code for libelf version 0.8.6 can be found at the following URL:
http://directory.fsf.org/libs/misc/libelf.html.
Source code for perfctr 2.6.31 can be found at the following URL:
http://user.it.uu.se/~mikpe/linux/perfctr/2.6/
ld for binutils 2.17.90: In this release of Sun
Studio Express on the Linux platform,
the GCC linker is extended to process the .exception_ranges
ELF section in the same way it processes the .gcc_except_table
ELF section. The source code and the modifications (diffs) are available in the
install_directory/prod/src subdirectory.
7. Features That Have Been Removed in This Release
The following features have been removed in this release of the
Sun Studio software.
gvim
gvim is an advanced and configurable tool built to enable
efficient text editing. It is an improved version of vi. In the Sun Studio 8 through Sun Studio 11 releases,
gvim is integrated with the IDE as an optional editor. In the
Sun Studio 12 release and in this Express release, gvim is a
stand-alone component.
The gvim editor will not be supported in this release or future releases of
Sun Studio software. Developers using the Solaris OS can obtain
gvim from the Solaris companion CD or from the
»Open Source Software for Solaris web site.
Developers on both the Solaris OS and
Linux OS can obtain vim directly from the »vim open source community.
XEmacs
XEmacs is an advanced and highly customizable open source
text editor and application development environment. XEmacs is a
graphical tool that is often used as an IDE. In the Sun Studio 8 through Sun Studio 11 releases, XEmacs is
integrated tightly with the IDE. In the Sun Studio 12 release
and in this Express release, XEmacs is a stand-alone component.
The XEmacs editor will not be supported in this release or future releases
of Sun Studio software. Developers using the Solaris OS can obtain
XEmacs from the Solaris companion CD or from the »Open Source Software for Solaris web site.
Developers on both the Solaris OS and
Linux OS can obtain XEmacs directly from the »XEmacs open source community.
X-Designer
X-Designer is an interactive tool for creating Motif-based graphical user
interfaces. It provides facilities to design user interfaces, edit layout,
and create custom icons. X-Designer creates portable code that can be
compiled to run on both the Solaris OS and the Linux OS. In the Sun Studio 8
through Sun Studio 11 releases, X-Designer was loosely integrated with the IDE
and could be called from an IDE menu. The tool is
bundled with the Sun Studio 12 software and this Express release as a
stand-alone component and is not callable from the IDE.
X-Designer will not be supported in this release or future releases of Sun Studio
software. Developers might be able to obtain the tool and contract for
support directly from
»Imperial Software Technology, Inc. (IST).
8. Usage Tracking Enabled
Usage tracking provides a way for Sun software engineers to
collect information about how developers use Sun compilers and tools.
This information can then be used to improve future revisions of the
products.
Usage tracking is enabled in this Express release. Usage
tracking will not be enabled in the final release.
Usage tracking captures the compiler and tools command options
that you specify. Usage tracking also uses the uname -a
command to capture platform information and operating system
information from the runtime environment. No file names, directory
names, or macros are collected. For example, you might issue the
following command:
CC -DMACRO -L/directory1 -I/directory2 -Xa -O hello.cc
In this case, only the following information is reported back to
Sun:
CC -D -L -I -Xa -O
Each time a compiler or tool is invoked, the options that are used
are logged in the file /tmp/.UT... The log file is sent
to Sun software engineers if the file exceeds 10 Kbytes or is more than
24 hours old.
You can turn off usage tracking by defining the environment
variable UT_NO_USAGE_TRACKING before running any of the
Sun compilers and tools.
(with csh) % setenv UT_NO_USAGE_TRACKING
(with ksh) $ export UT_NO_USAGE_TRACKING
(with sh) $ set UT_NO_USAGE_TRACKING; export
UT_NO_USAGE_TRACKING
Print-friendly Version
