RVCT 4.0 Build 471 patch for Windows

RVCT 4.0 Patch Build 471 for Windows Release Notes
==================================================


Description
-----------


This RealView Compilation Tools (RVCT) 4.0 patch #1 is intended for use with RealView Developer Suite (RVDS) 4.0 products. 
It can be used to update any RVDS 4.0 Standard, Professional or Evaluation installation, whether previously patched or an original installation. 
It is NOT compatible with previous (3.1 or earlier) releases of RVCT/RVDS or Keil MDK products.


This patch consists of updated RVCT/RVDS 4.0 compiler, linker, assembler, fromelf, and armar Program executables; updated Include files and updated C/C++ libraries.
The client licensing code for Windows and Linux executables is updated from FLEXnet 10.8.5.0 to FLEXnet 10.8.7.0.
This patch is now additionally validated for use on Windows XP SP3.




OS Platforms Supported
----------------------


This patch has been tested on the following supported platforms:


Windows XP SP2, 32-bit & 64-bit
Windows XP SP3, 32-bit
Windows Vista Business Edition SP1, 32-bit & 64-bit
Windows Vista Enterprise Edition SP1, 32-bit & 64-bit
Windows Server 2003 32-bit & 64-bit
Red Hat Linux Enterprise 4 for x86, 32-bit & 64-bit
Red Hat Linux Enterprise 5 for x86, 32-bit & 64-bit




Installation Instructions
-------------------------


To install the patch carry out the following steps:


1) Ensure that you are currently using RVCT 4.0.  To do this, type:
      
     armcc --vsn
        
   and ensure that this returns RVCT 4.0 build 400 or later.
      
2) Extract all the files from the ZIP file into a temporary directory.
   
3) Copy the include directory from the temporary directory to replace your 
   existing include directory. The default location is:
   
     C:\Program Files\ARM\RVCT\Data\4.0\400\include\
   
4) Copy the lib directory from the temporary directory to replace your 
   existing lib directory. The default location is:


     C:\Program Files\ARM\RVCT\Data\4.0\400\lib\
     
5) Copy the win_32-pentium directory from the temporary directory to replace
   your existing win_32-pentium directory. The default location is:
   
     C:\Program Files\ARM\RVCT\Programs\4.0\400\win_32-pentium\


   If necessary change the unzip destination directory to match the location 
   where you have installed the tools.
      
6) The updated tools should now have been installed. To confirm this, 
   open a DOS command prompt window and enter:
   
     armcc --vsn
     armlink --vsn
     armasm --vsn
     fromelf --vsn
     armar --vsn
      
     The version returned should be RVCT 4.0 build 471.




Changes From Previous Releases
------------------------------


RVCT 4.0 patch build 471 includes the following corrections and improvements since RVCT 4.0 build 400:




Compiler (armcc):
--------


The compiler now works around Cortex-M3 erratum 602117 involving LDRD when the base register is also the first loaded register.  The C/C++ libraries have also been rebuilt to avoid these instructions.


Some code size and performance improvements have been made to the Profile Guided Optimization mechanisms.


Some code-generation and optimization improvements have been made for NEON compilation.


Some compatibility improvements have been made when compiling for --gnu and --arm-linux, for example:
- The compiler now correctly translates the -mfpu=neon and -fno-inline options in gcc translation mode.
- Better approximate translations for the GCC floating-point optimization options have been added.
- Some aliases for GCC command-line options were not correctly translated
- The compiler now correctly recognises glibc setjmp variants with --library_interface=aeabi_glibc and generates correct code in the presence of these calls.
- The compiler did not correctly allow default symbol visibility to be overridden in ARM Linux modes.
- The gnu __builtin_va_... functions are now implemented
- When configuring the compiler for ARM Linux based on an existing GNU toolchain all paths are now checked for libraries that were specified by name only.
- The GNU builtins __builtin_powi, __builtin_powif and __builtin_powil are now translated correctly.


Some corrections have been made to the DWARF debug information generated by the compiler.


Some further TI C55x intrinsics have been added into c55x.h.


The compiler can now generate code that will catch a bad_typeid exception thrown from use of the typeid operator.


For embedded assembler (__asm) functions marked as __weak, the compiler no longer generates a weak reference from C code, to ensure the definition is not lost. A weak symbol is still generated in the assembler output.


In addition to recognizing files with extension .i as preprocessed C source (i.e. source for which preprocessing should be suppressed), the compiler now recognizes .ii as indicating preprocessed C++ source.


Some code generation issues have been addressed.


The compiler is now able to recognise more opportunities to use PKHTB instructions with ASR shift and PKHBT instructions with LSL shift.


The compiler now generates LDRD/STRD for volatile accesses of 64 bit data types.


The use of __declspec on classes is no longer ignored.


Some possible causes of the following internal faults have been fixed:
0x15f950, 0x298170, 0x3dd550, 0x44784c, 0x4ccb3b, 0x9c3725, 0x974f57, 0xafee20, 0xeeed90, 0xf28d9c.




C/C++ Libraries:
---------------


The variant of float.h provided for use with ARM Linux in the $RVCT40INC/arm_linux directory has been changed. By default, this defines FLT_ROUNDS to 1 meaning round-to-nearest, and this corresponds to GCC behaviour. However, this is not in strict accordance with ISO C. To conform to the standard, the FLT_ROUNDS must expand to an expression whose value changes with the floating point environment. An alternative definition of FLT_ROUNDS is provided if you need this strict ISO C behaviour. This is enabled by defining the macro __ARMCC_STRICT_FLT_ROUNDS when compiling your source code. This variant of the macro uses a call to fegetround(), so you must link with the glibc math library (libm.so or libm.a) if you use this variant.


The variant of float.h provided for use with ARM Linux incorrectly referred to __ieee_status().


arm_neon.h no longer defines __const as a macro, which prevented it from being used as a synonym for const in --gnu mode.


A wrapper for the glibc header file sys/cdefs.h has been added to $RVCT40INC/arm_linux. This is to avoid use of the GCC 4.3 builtins __builtin_va_arg_pack and __builtin_va_arg_pack_len, which are not supported by armcc.


In the STL implementation supplied with RVCT, and could sometimes fail to propagate an exception thrown by an allocator. This is now fixed.


_Bool is no longer predefined in C++ mode, as this breaks C++ code that helpfully uses "typedef bool _Bool;". It is still defined in C mode, as documented.




Assembler (armasm):
---------


A new --cpu option for v7-A + Security Extensions has been added ("--cpu=7-A.security") which allows the use of SMC (formerly SMI) instruction when assembling for the v7-A architecture.


A regression in the behaviour of armasm --diag_warning=1722 to downgrade the error for labels in IT blocks when assembling for Thumb-2 has been fixed.


Conditional BKPT instructions are now faulted within Thumb IT blocks because BKPT is always unconditional only.


The assembler no longer incorrectly diagnoses some valid ARM data-processing instructions as unpredictable or deprecated.


The assembler is now able to warn if an ATTR directive has not been applied.


A problem with the use of RELOC with a symbol defined by EQU has been fixed.




Linker (armlink):
------


"Linker feedback" was failing with main() being reported as unused because the call from the C library initialization code to main() was not being detected. This is now fixed.


The linker's callgraph output could show a called function as being "unused" when there were non-branch relocations in the section and more than one symbol at the same address as the destination symbol. This has been fixed.


The linker callgraph now correctly detects tail-calls that have been transformed into a nop by the linker. Previously these calls could be missed which would cause the tail-called function to be marked as unused.


Sections from object files containing a "." are now handled correctly in scatter-files, for example, "foo.bar.o" no longer matches with "foo.o".


The linker can now generate warning L6784E when data extends to outside the given section.


The linker is now able to report error L6221E for execution regions in scatterfiles which overlap with other regions (such as OVERLAY regions) that do not have region table entries.


armlink Internal fault 0xb4652d no longer occurs when the presence of ARM or Thumb code in the input objects does not match the Architecture derived from the Build Attributes of the image.


When building Linux applications, .note.ABI-tag SHT_NOTE sections from objects are now processed in the same way as .note.ABI-tag sections from shared objects.


A new command line option --gnu_linker_defined_syms has been added. This option is enabled when --arm_linux is in use, otherwise it is off by default.  
When this option is on the linker will support the GNU equivalent of Input section symbols:
__start_SectionName (RVCT Equivalent=SectionName$$Base)  - Address of the start of the consolidated section called SectionName.
__stop_SectionName  (RVCT Equivalent=SectionName$$Limit) - Address of the byte beyond the end of the consolidated section called SectionName
Note that a reference to SectionName by a GNU input section symbol is sufficient for armlink to prevent the section from being removed as unused. A reference by a RVCT input section symbol is not sufficient to prevent the section from being removed as unused.


A new command line option --[no_]add_shared_references has been added. This option is enabled when --arm_linux is in use, otherwise it is off by default.
This option affects the behaviour of the --sysv mode. If --add_shared_references is set then when linking an application the linker will add references from shared libraries. The linker will give an undefined symbol error message if these references are not defined by the application or by some other shared library. These references can be satisfied by static 'ar' format libraries.
Note: A reference from a shared library can only be satisfied by a symbol definition with protected or default visibility, as these are the only symbols that can be exported into dynamic symbol tables. The linker will give an error message if the symbol reference is resolved by a symbol with hidden or internal visibility.


A default visibility symbol that is given a local symbol version by a symbol versioning script, is no longer exported to the dynamic symbol table unless it is required for relocation. In previous armlink versions, the symbol would be exported with a local version.


For each shared library that a program depends on the linker will add a DT_NEEDED tag into the dynamic segment. A program loader such as ld.so will read these dependencies and automatically load these shared libraries. The order that the libraries is loaded in is sometimes significant so the linker will match the order of DT_NEEDED tags with the order the libraries appear on the command line. In the release version of 4.0 this order can sometimes come out incorrect with the library intended for position 2 in the list coming in position 3. This should only be significant if the library in position 2 needs to preempt symbols in the library in position 3.  This problem has now been fixed.




ELF Format Convertor (fromelf):
--------------------


"fromelf --compare sections" no longer fails with Internal fault 0x0ad3f4 when comparing two files whose zero-initialised data sections differed in length.


An issue in fromelf which resulted in a crash when processing libraries (containing multiple objects) has been resolved.


fromelf -ec on executable images now shows correct offsets in references from exception tables to code.