RVCT 4.0 Build 821 patch for Linux

Elecfans管家 当前离线 经验 3163 窥视卡 雷达卡

Elecfans管家 ( 楼主 ) 2014-10-20 10:54:58  只看该作者 3464 | 0 倒序浏览

分享地址：百度云盘http://pan.baidu.com/s/1B5il4

RVCT 4.0 Web Patch #7 Build 821 Release NotesDescription

This RealView Compilation Tools (RVCT) 4.0 Web Patch #7 Build 821 is intended for use with RealView Development 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 other 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, include files and C/C++ libraries.

Enhancements since RVCT 4.0 build 771General enhancements

• The tools now support --cpu=7E-M to generate code for the 7-M architecture enhanced with DSP (saturating and 32-bit SIMD) instructions as featured in the Cortex-M4 processor. [736675]
• Armlink now supports a new sorting type: --sort=LexicalState. This sorts all Thumb code before ARM code and then sorts lexically. [738147]
• Armlink now supports a new switch --[no_]crosser_veneershare. The default is --crosser_veneershare which keeps the existing behaviour of allowing veneer sharing across execution regions. --no_crosser_veneershare prohibits veneer sharing across execution regions. [737516]
• Armlink now supports the option --emit-non-debug-relocs. This functions like --emit-relocs but outputs only relocations from non-debug sections. [737515]
• Added new linkeroption --veneer_inject_type= where can be either or . The default is . The option controls the veneer layout when --largeregions mode is on. When --veneer_inject_type=individual the linker will place veneers so that they can be reached by the largest amount of sections that use the veneer. Veneer reuse between Execution Regions is permitted. This type minimises the number of veneers that are required but disrupts the structure of the image the most. When --veneer_inject_type=pool the linker will collect veneers from a contiguous range of the Execution Region and place all the veneers generated from that range into a pool placed at the end of the range. A large Execution Region may have more than one range and therefore more than one pool. This type has much less impact on the structure of image but has less opportunities for reuse as a range of code cannot reuse a veneer in another pool. The linker calculates the range based on the presence of branch instructions that the linker predicts may need veneers. A branch is predicted to need a veneer when a state change is required, or when the distance from source to target (plus a contingency) is greater than branch range. The size of the contingency can be set with the --veneer_pool_size=. By default it is set to 102400 bytes. The --info=veneerpools option provides information about how the linker has placed veneer pools. [737514]
  Added a new linker option --tiebreaker= where is either creation or cmdline. A tiebreaker is used when a sorting algorithm needs a total ordering of sections. The default tiebreaker is creation, which is the order of creation of the section data structure within the linker. The alternative --tiebreaker=cmdlineis the order that the section appears on the command line. The command line order is defined as File.Object.Section where 'Section' is the sh_idx of the section within the object. 'Object' is the order that the object appears within the file. 'File' is the order the file appears on the command line. The order that the object appears within the file is only significant if the file is an ar archive. To alter the format of mapfile (generated by --map) to show command line order use the --section_index_display=cmdline switch. [737517]
• The linker now supports additional options for controlling placement of .ANY sections. There are two new command line options: --any_sort_order= where is either descending_size (sort in descending size order) cmdline (sort by command line index) The default is descending_size. --any_placement= where can be first_fit (place the section in first ER with space), best_fit (place the section in ER with least free space, worst_fit (place the section in ER with most free space), or next_fit (place the section in current ER if there is sufficient space, or move to the next ER in the scatter file if there is insufficient space. Never back-track to previous ER). The default is worst_fit. Additionally a new info option has been added: --info any. This will output the sort order, assignment algorithm, and which sections are assigned to which execution region in the order that they are processed by the placement algorithm. [737513]
  
  

OS Platforms

This patch has been tested on the following supported platforms:

• Windows 7
• 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
• Solaris for SPARC 10
  
  

In addition, the patch has been tested on the following non-supported platforms:

• Windows 2000 SP4
• SUSE Linux 9.2
• Ubuntu Linux 8.10
  
  

Installation Instructions

To install the patch carry out the following steps:

• 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.
  
• Extract all the files from the ZIP file into a temporary directory.
• Copy the include directory from the temporary directory to replace your existing include directory. The existing directory can be located by the RVCT40INCenvironment variable, e.g:

  > echo $RVCT40INC
  ~/ARM/RVCT/Data/4.0/400/include/

• Copy the lib directory from the temporary directory to replace your existing lib directory. The existing directory can be located by the RVCT40LIB environment variable, e.g.:

  > echo $RVCT40LIB
  ~/ARM/RVCT/Data/4.0/400/lib/

• Copy the linux-pentium directory from the temporary directory to replace your existing linux-pentium directory. The existing directory can be located by the RVCT40BINenvironment variable, e.g.:

  > echo $RVCT40BIN
  ~/ARM/RVCT/Programs/4.0/400/linux-pentium/

• 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 821.
  
• After unzipping the executables, you may find that they cannot be executed because the UNIX permissions have been reset. The workaround is to set the execute permissions for the user with, e.g.:

  chmod u+x armcc

  
  
  

Corrections since RVCT 4.0 build 771Compiler (armcc)

• A code generation issue that generated a dereference to uninitialized pointer is now fixed. [734706]
• Warnings and errors have always been suppressed in system header files. They are now also suppressed in the corresponding implicitly included template implementation files. [736105]
• When using --remarks, passing a wide string (L"abc") to a printf function could generate a remark #181 about incompatible printf argument even if the corresponding format string was "%ls". The remark now does not occur in this situation. [735496]
• When using --multibyte_chars in GNU modes, the compiler might detect a spurious line concatenation character when a line ended with a multibyte character (e.g. in a comment) followed by one or more whitespace characters. When using C++-style trailing comments, this might cause incorrect interpretation of source code. [737748]
• In GNU C++ mode, use of compound literals (a C99/GNU extension) to initialize file-scope variables could result in runtime failures. This is now fixed. [736266]
• Some small corrections have been made to GCC command line translation. [735554]
• A cause of internal fault 0xe70a0c with -g --remove_unneded_entities has been fixed. [738296]
• A cause of internal fault 0xfe1945 and 0x0d9189 at -O3 -Otime has been fixed. [737716, 735852]
  
  

Assember (armasm)

• The new option --branchpatch=cortex-a8_q109 has been added to work around a Cortex-A8 bug by inserting NOPs to avoid a wide branch spanning a page boundary. [736360]
  
  

Linker (armlink)

• Armlink could assign an incorrect type to .dynstr sctions, which could result in fromelf generating error Q0454E. This has been fixed. [732898]
• Armlink will now process old-style region tables correctly. Previously under certain circumstances armlink would fail to link images which implemented their own scatterloading mechanism using old-style region tables, exiting with "ARM Linker: Execution interrupted due to an illegal storage access". [734549]
• Armlink will now report error message L6065E when failing to a write contiguous block larger than the maximum of 2GB. [728400]
• Armlink now orders .fini_array sections correctly in --sysv images to ensure destructor functions are executed in the correct order. [737347]
• Armlink callgraphs give enhanced function pointer information and combine multiple calls to the same function pointer from the same section. [736849]
• The linker no longer tries to check out two licenses when linking with --ltcg. [737667]
• Armlink will generate long branch veneers for branches from position independent code in a 'PI' execution region to targets in an 'Absolute' execution region. By default armlink was not reusing these veneers leading to a large code-size increase. This has now been fixed and armlink will reuse these veneers when it is safe to do so. [738802]
  
  

C/C++ Libraries

• The full Unicode wide-character ctype functions towupper() and towlower(), if enabled with #pragma import __use_utf8_ctype and #pragma import __use_full_wctype, and if compiled using --wchar32, would return the wrong answers for the character pair U+1D79 and U+A77D, which should be lower-case and upper-case versions of each other. [736950]
• In strict C++ mode, and no longer declare the FILE type. Also, the macro __ARM_WCHAR_NO_IO can now be defined to cause these headers not to declareFILE or the wide I/O function prototypes. [733711]
  
  

ELF format converter (fromelf)

• Sometimes, fromelf --bin would name an output file after an unrelated SHT_NOBITS section which shared the same file offset as the segment contained in the file. [735346]
  
  

Multiple tools

• When producing DWARF debug information, the assembler and compiler could output CIE and FDE records that had a length that was not a multiple of four, which can cause problems for third-party debug tools. This has now been fixed to produce padding in the appropriate places. [733101]
• --cpu=Cortex-M4.fp now sets the predefined macro __TARGET_CPU_CORTEX_M4, not __TARGET_CPU_CORTEX_M4_FP as previously. The presence of FP can be tested using the__TARGET_FPU_VFP macro. [736497]
• In Japanese message locales, when using --diag_style=ide, the comma between file line and column is now an ASCII comma rather than a Kanji comma. [736125]