Tool News
 
 
 

Tool News

Products Info
Downloads
Tools FAQs
MESC TOOL NEWS: MESCT-AS79-991216D

AS79
Precaution

Please take note of the following problems in using relocatable assembler AS79 for the 7900 series of microcomputers.

  1. Versions Concerned
    AS79 V.1.00 Release 1 -- V.3.20 Release 1 (AS79 included with C compiler NC79WA for the 7900 series MCUs is also concerned.)

  2. Problem in as79
    2.1 Description
    When the default optimization level for jump size configured in as79 is used, the following error message is displayed if optimized jump processing is undefined:
    [Message Displayed]: jump optimaize pass exceeded, non-optimize jump size selected

    2.2 Workaround
    Change the optimization level with as79's command option "+optpass=" as follows:

    When the change is made on as79: as79 +optpass=50 test.a79
    When the change is made on nc79: nc79 -c -as79 "+optpass=50" test.c

    The notes concerning the above command option "+optpass" are described below:
    (1)Any value within the range of 0 to 100 is available as an optimization level.
    (2)If a value outside the above range is chosen, the default optimization level takes effect, instead. The default optimization level in each version of as79 is shown in the following table:
    Version of AS79 Default Optimization Level
    V.1.00 Release 1 -- V.3.10 Release 2
    7
    V.3.20 Release 1
    20

    (3)The command option can be placed anywhere in the command line.


  3. Problem in ln79
    3.1 Description
    When the linker is invoked with a command file selected, the relocatable file or command parameter before the end-of-file code (EOF) cannot be executed unless a hard break is inserted prior to the EOF.

    3.2 Example
    In the following command file, "file2" cannot be executed:
    ------------------
    file1 file2[EOF]
    ------------------

    3.3 Workaround
    Be sure to place a hard-break code at the end of the final line of the command file as follows:
    ------------------
    file1 file2[RET]
    [EOF]
    ------------------

    3.4 Schedule of fixing problem
    We plan to fix this problem in our next release.




© 2008. Renesas Technology Corp., All rights reserved. Privacy | Legal