Rational Apex Embedded Solaris to PowerPC Family Release Note for LynxOS

This release note applies to Release 4.2.0 of Rational Apex Ada 95/83 for LynxOS. Full instructions for using this product are provided in Programming for LynxOS.

This document contains only release notes specific to LynxOS cross-development. Release notes for the parts of this product that are also applicable to the native Apex product are provided in the Rational Apex Release Note.

Note: Starting with the 4.0.0 releases, the rada executable used to code Apex Embedded Ada views is the same executable shipped with the native product (Please check the native Apex patch descriptions for possible newer versions of rada).

The "latest" Release Notes for LynxOS can be viewed on–line.

• Host and Target Specifications
• Documentation
• New Features in Release 4.2.0
• Introduction to Cross-Development for LynxOS
• Special Considerations
• Installation Requirements
• Installing the LynxOS Cross Development System
• Installation For C/C++
• Installation For AXI Bindings
• Known Limitations
• Defects Resolved in Release 4.2.0

Host: Sun SPARC workstations running Solaris 2.6, Solaris 7, or Solaris 8.

Target: LynxOS 3.1.0a or 3.1.1, PowerPC CPU with a patch set that addresses LynxOS Reference Numbers 16705 and 16727 (See Note 1). There are also potential problems using the Apex debugger with LynxOS 3.1.1 (see Note 2).

Note 1: For the gen1 BSP, this is patch level 27. Patches for other BSPs may or may not be available at this time. Contact LynuxWorks to get the right patch for your target BSP. Without the correct patch installed, programs linked with the Ada runtime libraries will cause a core dump when any predefined exception is raised.

Note 2: Some versions of the LynxOS 3.1.1 BSP for the DY4 SVME179 have exhibited problems in the Apex debugger which can lead to kernel crashes when trying to debub an Apex program. The GDB debugger supplied with LynxOS 3.1.1 has similar problems using this BSP. Contact LynuxWorks to get the right patch for this BSP.

Embedded Programming Guide for LynxOS
Release Note for LynxOS (this document)
Command Reference
Utilities Guide

These documents are available in online format. They can be accessed through the Help > Manuals command. Postscript versions of the documents can be printed using the Help > Print Manuals command.

There is a new tab in the File > Run and File > Debug dialog boxes. The tab is labeled Browse.

The Browse tab enables the user to view their application in the GUI debugger without actually running (or even loading) the program onto a target. In fact, the user does not need a target at all to use the GUI debugger in this way.

The Browse tab contains an optional Stack Trace Dump text field. If the user has generated a stack trace dump they can supply the generated file in this field, and will then be able to use the debugger to navigate the call stack.

Stack trace functionality has been added to the Apex 4.2.0 release. See the "Exception Handling" chapter in Using the Ada Runtime for more information.

Apex now systematically assigns a short, unique prefix to task names. The full task name, including the prefix, can be obtained at execution time from Ada.Task_Identification.Image. This name is also passed to LynxOS when the thread implementing the task is created, allowing the names to be displayed with the LynxOS ps command using the -t option.

The OS truncates the full task names, but the unique prefix will usually be visible. The debugger now provides a task_id flag that can be set to display these names using the lt command.

Further details can be found in the "Tasking" chapter of Using the Ada Runtime.

Starting with the 4.0.0 release, the rada executable used to code Apex Embedded Ada views is the same executable shipped with the native product (Please check the native Apex patch descriptions for possible newer versions of rada). The code generator apex_ada_cg_phase and optimizer apex_ada_optim_phase executables are not shared. The location of the rada, apex_ada_cg_phase and apex_ada_optim_phase executables are determined from the view the user is coding in. The apex_compiler_tool script can be used to determine the location of these tools. For example:

% apex_compiler_tool -show_tools
/tools/rational/releases/apex.4.0.0b/sun4_solaris2/bin/rada
/tools/rational/releases/apex_embedded.4.0/bin/power/lx/apex_ada_cg_phase
/tools/rational/releases/apex_embedded.4.0/bin/power/lx/apex_ada_optim_phase

Apex Embedded provides many $APEX_BASE/ada/model.ss views with each release. The view names can be long and their meaning can be obscure. To help make sense of the information encoded in the view name, each model is now shipped with a description file. The description files explain what the cryptic portions of the view name mean.

This description can be viewed from the command line by invoking the properties command with the -model_info option. The properties command can specify a model.ss view directly, or another view modeled on a model.ss view.

The description can also be viewed from the GUI. Dialogs that ask the user to select a model (e.g. File > New > New View) have a navigation icon next to the text field. Clicking the navigation icon displays the Model Navigator dialog. Once a specific model has been selected within the Model Navigator dialog, the model description file will be displayed in the "Information on selected model" section.

The following four dialogs have been combined into a single dialog.

• File > Run
• File > Debug
• File > Download
• Tools > Targets

Each function is still accessed via the menus above. Once the dialog appears, users can switch between the four functions by selecting tabs within the dialog.

The Control > Maintenance > Upgrade To New Release dialog and corresponding apex_upgrade script are part of the Apex Native product. Starting with the 4.0.0B Native Apex release, this dialog and script now work for Apex Embedded.

Users can now link, run, and debug programs from within Clearcase.

Customers can purchase source releases of Apex Embedded products. These source releases include full source to $APEX_BASE/ada/*.ss/*.rel views (no API's) including the views used to create the runtime archives.

The File > New > New Source Release dialog can be used to make a copy of the entire set of views so that development work will not alter the installed product.

When doing development that effects the runtime archives, it can be difficult to determine what views need recoding, and what runtimes need re-linking after source code changes have been made. To simplify this process, we have created the apex_create_libraries command. The syntax of this command is simple. You point it at the directory containing links to all the runtimes archives (i.e. the directory identified by a model's RUNTIMES switch) and it takes care of coding views, and re-linking archives.

The default alignment of types and objects has changed in Apex 4.0.0. Be aware that in the absence of representation clauses specifying the alignment of a type or object, the compiler is free to choose the optimal alignment with respect to performance. See the Apex native Release Notes for more details.

The Ada Runtime for Apex 4.0.0 has been migrated to POSIX 1.c under LynxOS 3.1.0.

The Rational Apex 3.2.0 Embedded Solaris to PowerPC for LynxOS product supports LynxOS 3.0.1. This version of LynxOS does not support the POSIX_THREAD_PRIO_PROTECT mutex locking protocol. As a result, Apex 3.2.0 implements protected objects compiled with pragma Locking_Policy (Ceiling_Locking) with a combination of PTHREAD_PRIO_NONE mutexes, which have no effect on thread (and therefore task) priority, and explicit priority change using pthread_setschedparam(). This is not fully compliant with the Ada real-time scheduling as specified by pragma Task_Dispatching_Policy (Fifo_Within_Priorities), since explicit priority changes move the thread to the back of the scheduling queue for its priority, where loss of ceiling priority should leave it at the front of the queue. The result is that a task incorrectly yields the processor to other tasks of the same priority when completing a protected action.

The corresponding Apex 4.0.0b product supports LynxOS 3.1.0a which does support POSIX_THREAD_PRIO_PROTECT mutexes. The Apex 4.0.0 runtime for LynxOS has been modified to use these mutexes, eliminating explicit priority changes when completing a protected action. Loss of ceiling priority when unlocking a mutex using this policy leaves the thread at the head of the queue for its priority, as required by the Ada Fifo_Within_Priorities scheduling policy.

Ada.Asynchronous_Task_Control, previously found in views in the Real_Time_Systems subsystem has been removed because it cannot be fully supported on a LynxOS target.

Apex 3.0.1 for embedded platforms included the package Language in the rational.ss subsystem. This package provides constants useful for interfacing to other language implementations on those platforms. For example, the prefix character added to link names by those language implementations.

The function of this package has been superseded by the Apex implementation of the Import, Export, Convention, and Calling_Convention pragmas. In particular, the compiler will treat the External_Name argument to the Import and Export pragmas as a name in the target language and perform the necessary modifications to that name to create the corresponding link name. Note that no modifications are made if the Link_Name parameter is used instead of External_Name.

These features make the Language package obsolete for the Apex embedded products. It has therefore been removed from 3.2.0 and later embedded releases.

In embedded VADS programs Ada address clauses for with static addresses were represented by a linker group to prevent overlapping use of the memory associated with address clause variables. This feature is no longer supported by the Apex compiler. The Apex compiler allocates a pointer to the address specified in the address clause and all accesses to the variable are implemented as indirect references through this pointer.

In some circumstances the optimizer is able to optimize away the pointer and make references directly to the specified address. There is no mechanism to assure that the specified memory address isn't allocated by the linker to some other part of the user program.

For a complete description of the following commands see the Programmer's Guide.

apex_execute

The new version of apex_execute differs as follows:

• It has a -help option.
• It can take a -logical_target parameter (though if this parameter is not specified, the LOGICAL_TARGET_NAME switch for the enclosing view).
• It is written in apex shell, not cshell.

apex_simulator

The new version of apex_simulator differs as follows:

• has a -help option.
• is written in apex shell, not cshell.
• has a -sim_file option which allows you to override the default selection.
• has a -logical option which allows you to map the simulator to a logical target as part of the apex_simulator command.

apex_add_target and apex_target_control have been replaced with the new commands mentioned above.

The following debugger enhancements are now available:

• Target initiated debugger connection simplifies target configuration (removes the gdbserver port field in the target dialogs).
• Program Input/output that is identical to the rest of the Apex embedded product line.
• Asynchronous attach to a running program.
• Less intrusive debugging of tasking applications due to less interaction between the target and the debugger during normal operation.
• Serial debugging.
• Proxy debugging.

Attaching task entries to interrupts has been made operational on all architectures.

The LynxOS debugger can now attach onto a running process.

To use this feature you must first obtain the thread id of the running process. Logon to your LynxOS target and execute the following command.

> px xat

Now from the debugger dialog, specify the tid of your thread in the attach field provided.

You can also run the debugger from the command-line

$ apex_debug -a 15 hello

The runtime for LynxOS is internally compatible with the other pthreads implementations. Although not user visible, this internal sharing provides a more reliable implementation of LynxOS with many bug fixes that have been leveraged from the other pthread environments (Solaris, HP, SGI, OSF, and AIX)

All of the runtime archive and predefined components have been compiled at optimization level 2 with the optimization objective set to space (instead of time). This provides the smallest footprint for embedded applications as well as the best performance.

Target Control has been restructured for the 3.2.0B release. New target control gui implementation allows physical targets to be globally visible resources for a development team yet still allow individuals to reserve individual physical targets. Multiple targets can be manipulated from the same Apex session.

Please read the Target Control Chapter in the Programming Guide and refer to Getting Started.

ACVC validation test suites are certified at optimization levels 0, 1 and 2 with optimization objective of SPACE.

With Apex, cross-development for a LynxOS target is almost identical to native Apex development. The primary difference is that the resulting executable code runs on a target machine which is different than the development machine.

The same Apex user interface is used for both native and cross development. Thus, editing, navigation, compiling, and even linking proceed using the same key and mouse sequences.

In order to run the target program, it must be copied to the target machine and executed there. Fortunately, Apex automates these steps, so the run and debug commands operate in virtually the same manner as they do for native development. Internally, of course, the commands perform additional steps.

When running your executable, Apex opens two xterms: one shows the progress of the steps required for execution, and the second logs in to the target. When the program has completed, you must enter Exit on the target xterm. You can then close the first xterm by entering Control-C.

There are some special considerations for LynxOS cross-development. These considerations arise from the fact that developing for LynxOS is cross-development, but the target is a full-featured OS with most UNIX features, rather than a processor board. LynxOS development shares characteristics of native and cross development.

1 . When running Apex tools, especially the debugger, remember that while the tool runs on the host, the resulting executable program runs on a different machine.

The most obvious instance of this is standard input and output. When using the debugger, the program actually writes its output on the target.

2 . Similarly, with LynxOS, the file system is on the target. For example, if your program opens and writes to a file named temp.tmp, the file is on the target.

For native development, the host is the same as the target, so the file ends up on the host system itself. For most versions of Apex cross, the target is a separate machine but the file system is simulated on the host. (This feature makes it easier to develop test software or diagnostic tools.) In either case, if you are used to developing with Apex, you may be used to having file I/O end up on the host system.

3 . The final link step uses the LynxOS cross-linker.

A third-party linker is invoked for LynxOS cross development. This technique allows the Apex user to use the target linker developed by the vendor and thereby maximize the compatibility with third-party and OS-specific libraries which are typically targeted to that linker. This is different from most Apex crosses, where Rational supplies an embedded linker.

The downside of this strategy is that some third-party linkers are not very helpful in diagnosing link-time problems. The Lynx cross-linker is no exception. Apex is able to diagnose problems only through the prelinking phase. The tools $APEX_LYNX_ROOT/usr/bin/nm and objdump are especially helpful in diagnosing link problems.

4 . Apex uses rcp to copy the executable to the LynxOS target. Thus, each developer must have a login on this target, along with rcp privileges.

5 . Apex logs onto your target machine using expect. This tool assumes that your login prompt on the target is "% ". If it does not recognize your prompt, run and debug will probably work, but with long delays. Setting your prompt to end in "% " will avoid delays.

To develop code for a LynxOS target, you must have the following installed. Specific versions for these can be found in Host and Target Specifications

• Apex Ada 95/83 Sun SPARC Solaris.
• Apex Ada 95/83, Sun SPARC Solaris to LynxOS PowerPC (this product). This product is installed as an add-on to the native product.
• LynxOS Cross Development System for Sun SPARC Solaris, PowerPC target.

• LynxOS.

In order to debug programs running under LynxOS, a special debug daemon must first be downloaded to your Lynx target. This daemon is called gdbserver.

The blueprint for copying gdbserver to your Lynx target is:

% apex_load_gdbserver LYNX_TARGET:REMOTE_SERVER_LOC/gdbserver

Replace LYNX_TARGET with the name (or IP address) of your Lynx target. Replace REMOTE_SERVER_LOC with a fully rooted path to the existing directory where you want to put the gdbserver. Then execute the command from an Apex shell.

Instructions for installing Apex tools are provided in the Installation Guide.

When Apex for LynxOS is installed, the value for the environment variable $APEX_LYNX_ROOT is defined. Apex uses this variable to find components of the LynxOS Cross Development System. On LynxOS 3.0.0, the usual value for $APEX_LYNX_ROOT is:

/usr/lynx/3.0.0/ppc/cdk/sunos-xcoff-ppc

There is one additional step specific to LynxOS development which must be completed. This step is the installation of the LynxOS Cross Development System. Apex uses its linker and the LynxOS system libraries.

Follow the instructions in the LynxOS documentation for doing this.

Remember that you are installing this on the Solaris host, not the LynxOS target. The Solaris host is the machine that the Lynx Guide calls the "Cross Development Machine." Install for the "ppc" target.

The root for installing the files is /usr/lynx/version/ppc -- the same as $APEX_LYNX_ROOT/../..

Install both the "LynxOS Development Image" (*.devos_tape.tar.gz) and the "Cross Development Image" (*.cdksol1.tar.gz) for SunOS on the host machine.

Apex supports the development of C/C++ code for LynxOS as a separately licensed feature

The optional C/C++ views and tools are selected during the installation dialog. No additional setup is necessary.

AXI Bindings are provided to support development of X-Windows Applications. This is a separately licensed feature.

To install the bindings, select the optional Ada X Interface (AXI) product during the installation dialog.

One additional step is necessary. The LynxOS X11 libraries are required on the host in order to link. These can be copied from the Lynx distribution CD. On the CD, the support files for X-Windows development are found in:

/cdrom/tar_images/*.x11r6_tape.tar.gz
/cdrom/tar_images/*.motif_tape.tar.gz

Expand the tar files (using gunzip or a similar utility) and then use tar to extract the libraries.

% cd /usr/lynx/3.0.1/ppc
% tar xvf x11r6_file\
 usr/lib/libXmu.a  \
 usr/lib/libXext.a \
 usr/lib/libX11.a \
 usr/lib/libXt.a  \
 usr/lib/libSM.a  \
 usr/lib/libICE.a

% tar xvf motif_file\
 usr/lib/libMrm.a   \
 usr/lib/libXm.a    \
 usr/lib/libUil.a

Due to a limitation introduced in LynxOS 3.1.0a, a predefined Ada exception such as Constraint_Error or Program_Error may cause corruption of nonvolatile floating point registers. We anticipate that a future patch to LynxOS will resolve this problem.

Control-C (^C) does not work from within the debugger.

In the Rational Apex 4.0 Embedded Solaris to PowerPC for LynxOS product, for loops may fail to terminate in certain situations. Bcopy, a subprogram internal to the runtime, does not preserve the value of the CTR register, which is used in optimized for loops. Calls to Bcopy are generated by the compiler to copy large objects, e.g. for record or array assignment. If one of these calls is made in the body of an optimized for loop, it may zero CTR, which prevents the loop from terminating.

The circumstances under which this will occur have not been completely characterized. They are rare, and have only been observed at optimization level two. The runtime fix addressing this problem was not available at the time of the release, and will be included in the first patch to this product.

When using File > Debug, output is directed to an xterm. Make sure that you have an xterm executable on your path before starting your Apex session.

When debugging, the Input/Output window is replaced by a new one immediately upon program exit. Put a break at the last line of the program to preserve program output.

(Defect 127507) Running the debugger without first selecting a target under target control causes the debugger to fail. Workaround: Always run Tools > Target Control first.

Problems fixed in the base Apex product are listed in the release notes for the base product.

Refer to your product online documentation, Help > Manuals for the very latest updates to release notes.

Table 1 Defects Resolved in Release 4.2.0

Defect	Description
4482	STORAGE_ERROR raised when 'withing' task attributes but no tasks declared
4705	Embedded multi program not supported
5687	Activate / Deactive all breaks does not work.
6025	How can I save the size of the debugger source window.
6370	TestMate does not work on vw_i386: Sanity check fails
6668	main function return value not passed to $status
6779	"lt use" in the debugger always shows 99% used for the HEAP space
6793	Running a test list under debugger no longer works for Apex->LynxOS
7009	Apex 3.2.0b debugger cannot display tagged type on heap
7218	MCDC instrumenter does not treat deferred constants as literals
7325	"Update to new Release" updates customer imports
7334	tm_examples don't work with Apex Embedded 4.0 PPC for Rational Exec & Tornado
7335	Clicking Disassembly while dining philosophers is executing essentially hangs debugger
7339	must specifiy a program in download dialog in order to download kernel
7346	Convert dialog fails for sfp: "unsupported target_architecture ppc_eabi_sfp"
7348	"apex_execute.ash, line 1015: cpp_variant: Undefined variable" while debugging multi_main
7356	failed to exec the child process ev_formats.show
7415	tm_qualifications (etc) views empty for rx_ppc mark 400 product
7444	testmate.ss views for LynxOS ship with wrong histories for I/O
7448	problem with new Run/Debug/Download/Targets dialog in 4.0.0b
7456	"File:New:New Source Release" fails to create destination views
7464	Source Release views shipped as APIs
7465	Linking with link.map "on error" option always generates link map
7475	Problem compiling with immediate includes in Apex4.0 for LynxOS
7494	File : New : Source Release fails to correctly copy host_assist library
7510	Compile > Show > Disassembly gives poor error message for *.o files.
7512	post_instal 4.0.0b says "O/S version '5.8' does not match"
7513	Tools > Tornado Launch can compute WIND_REGISTRY incorrectly
7515	Inapropriate siennack warnings displayed when linking C stand-alone programs.
7519	File > New > BSP not working correctly under ClearCase
7520	Order in which views coded by File > New > BSP not always correct.
7530	Debugger malfunction when changing the value of a variable
7539	Installing Apex Embedded releases wipes out apex_embedded.4.0/bin
7540	Correct ada_examples.ss views for vw_ppc ada83
7550	ss_description.txt files missing from views
7555	tools->convert doesn't lists avaiable formats
7558	t3 daemons missing from C++ bin directory
7559	profiling does not work with Tornado 3.0
7569	Tools:Convert dialog doesn't initialize format buttons
7570	File:New:New Source Release documentation wrong
7571	Tools:Profiling initial Data File not always correct
7572	symbol info on .C file gives "Incompatible object file"
7573	das not found if show -> disassembly on .o file
7574	Fixed_Io.Put fails in PPC simulator w/software FP
7575	tools->symbol info window doesn't come up with correct runtime kind
7578	Debug Execution:Step_Instruction has "p" underlined
7579	file->new->new source release doesn't copy C views
7580	Tornado run and debug daemons are shipped with RX
7588	relative paths do not work for new->new source release
7594	solaris debugger can not disassemble fcmps %f1, %f2
7599	Examples are missing from tm_examples.ss for LynxOS
7612	Expected results change due to a change in TestMate logging
7624	Expected coverage kind message obsolete in tm_examples
7640	Handling predefined exceptions causes floating point register corruption
7652	tools->convert gives wrong option when converting to vox
7657	relocation info not available with Tools->Symbol Info when executable is selected
7660	v_i_int64."/" does not work if numerator < 65536*integer'first
7667	model information not shown when selecting source model for new->new bsp
7682	LynxOS Ada.Calendar uses old localtime_r()
7688	In TestMate user manual, oversimplified basic block description
7689	apex_execute.ash, line 203: Missing argument
7729	Threaded runtime doesn't retry on EAGAIN
7734	C threads can't call Ada tasking operations
7741	potential bugs with exception handling for interrupts
7743	Request for better task naming for LynxOS
7760	Stream_IO.Open/Close no longer cause a memory leak on repeated calls.
7776	Solaris cross 68k Rexec Enet - exception TASKING_ERROR
7780	"Unrecognized switch: -verbose_help" from apex_create_kernel_interface
7783	Coverage data is lost on unhandled exception
7789	Coverage pool overflow message is lost
7800	Apex 3.2.0b running out of pty's on HP 11.0
7808	C++ exceptions not caught in mixed Ada/C++ programs
7813	ERROR CREATING NEW BSP IN ACCI MODE
7817	changes to MVME2700 bsp for raven_pic PCI features
7817	changes to MVME2700 bsp for raven_pic PCI features
7828	TestMate>Setup does not work for C++ testmate models
7840	V_I_Sema package missing initializer
7843	Cannot reserve new simulator targets from the GUI
7844	Power.lx views shipped as Development, not Frozen
7853	Address representation does not work in 4.0.0b
7898	Poor performance for disassembly of PowerPC executables
7901	Constraint_Error in TCP/IP program
7907	Generate_Sigusr2 mistakenly generates Sigusr1
7915	Apex patching linker gets internal XLINK error
7928	Missing initialization messages when starting Apex Embedded
7950	Debugger can't handle two threaded programs on SGI
7962	ts0: Calls to interrupt level protected entries hang
7967	v_i_libop.movc3 does not resolve on Solaris
7967	v_i_libop.movc3 does not resolve on Solaris
7980	ApexRx 4.0.0b for PPC: Error in kernel:: Task context saved twice
7993	XLINK generates symbols with bad offsets
7997	Child process of Kernel Service Configuration dialog fails to exec on Solaris 8
8004	Creating new simulator may generate incorrect error
8022	Native debug dialog gets invoked from embedded view
8032	Linking errors with patch 20011132-1
8052	We deliver views with APP_DIRECTIVES set
8053	Bug in Ada RTS source
8090	convert -f ieee causes converter to core dump
8101	Undefined reference to \Q__DIV_I_64' at link time
8107	profiling fails with unexpected target signal from a.run_etdm
8111	Patch 200110012-1 leads to incorrect instrumentation of return statement
8120	# of storage elements allocated from a user-defined storage pool exceeds Max_Size_In_Storage_Elements
8120	# of storage elements allocated from a user-defined storage pool exceeds Max_Size_In_Storage_Elements
8126	problem in V_I_Int64.Div_64 (Split_64 )
8142	sched_get_priority_min does not check Policy value
8142	sched_get_priority_min does not check Policy value
8155	Segmentation fault in Storage_management.segments : procedure unlink
8160	Default Storage_Management locking deadlocks
8191	Storage_Management.Collections has unused variables and unnecessary type conversions
8194	Unused variables and unnecessary type conversions found in source code
8195	Unnecessary type conversions and unused variables found in source code
8196	TestMate Cross: Missing required key "bin/update_testing_tower"
8198	Alignment offset ignored by runtime system
8200	Apex 3.2.0b - dead code in rx_i386
8212	30 sec delay in Calendar packege
8216	Unreachable decision point after "end if"
8225	TestMate LynxOS 4.0.2 failure
8256	storage pool deallocation error
8259	apex_new_bsp's copy_view has quote problems
8292	Documentation for apex_create_libraries missing
8311	profiling doesn't provide any information
8312	profiling doesn't work under ada83
8313	Request for RTS source code matching the installed patches
8320	uninitialized variable used in Usr_Mbox.Mailbox_Read
8322	Debugger script doesn't handle -L option correctly.
8323	apex_new_bsp gives an error if source ss has empty value for SUBSYSTEM_NAME
8383	Exponentiation overflow in Modular_Multiply.2.ada
8388	dead code in usr_prog.2.ada
8391	rts_interface.ss, Package putil

Table 2 Defects Resolved in Release 4.0.0B

Defect #	Description
1814	Daylight Saving and Calendar
2859	Check_Config problem
5456	apex_symbol_info is broken for lynx and others?
5462	eTDM fails to init DEC21x4x correctly
5468	Single location for all timer configuration
5554	Comments in v_krn_conf.2.ada are wrong
5607	Floating point register corruption with mixed float types
5630	Link error with pragma Suppress(All_Checks) in separates
5863	Protected object failure
5980	apex_convert fails when relocating Srecords
6066	"The linker option ""Kernel"" is not used in Apex"
6129	LynxOS C++ linking documentation error
6255	"Ada.Real_Time (Time_Unit, Clock, etc.) configuration difficult, incomplete"
6293	Link error when importing C++ routine
6354	Cannot redirect input -- Apex Embedded for LynxOS
6369	System.Default_Bit_Order=High_Order_First for i386; should be Low_Order_First
6552	Internal Error: unable to generate /tmp/embedded_enviroment.10700
6590	disassembly of C objects does not work from the gui
6717	Imports between Ada and C/C++
6861	Lost parameters in a mixed Ada/C++ application
6878	Enabling C++ linking causes a segmentation fault at program termination (Lynx)
7099	Time_Error raised in Split during Daylight Saving Time change
7772	Improve runtime error reporting