 |
|
|
MESC TOOL NEWS:
MESCT-NC308WA-001101D
NC308WA, NC30WA, NC79WA,
AS308, AS30, and AS79
Precautions
|
|---|
Please take note of the following problems in using compilers (with an assembler and integrated development environment) NC308WA, NC30WA, and NC79WA; and assemblers AS308, AS30, and AS79:
- On concatenating strings in assemblers (AS308, AS30, and AS79)
- On the order of searching include files in assemblers (AS308, AS30, and AS79)
- Problem on Concatenating Strings in Assemblers (AS308, AS30, and AS79)
- 1.1 Versions Concerned
- Compiler/assembler for the M16C/80 series MCUs:
- NC308WA V.1.00 Release 1 -- V.3.00 Release 1
- AS308 V.1.00 Release 1 -- V.3.00 Release 1
- Compiler/assembler for the M16C/60 and M16C/20 series MCUs:
- NC30WA V.2.00 Release 1 -- V.4.00 Release 1
- AS30 V.2.10 Release 1 -- V.4.00 Release 1
- Compiler/assembler for the 7900 series MCUs:
- NC79WA V.2.00 Release 1 -- V.4.00 Release 1
- AS79 V.1.00 Release 1 -- V.4.00 Release 1
- 1.2 Descriptions
-
When more than one argument of a macro call is concatenated, the line numbers contained in the line information after the concatenation get different from those in the source program. As a result, the following symptoms appear:
- (1) If an error arises, the number of a line different from the one at which the error is detected will be displayed in the error message, which will prevent you from moving to the source line in question when the tag jump function is used in an editor and others.
- (2) Source level debug will not properly be performed in simulator debuggers and debuggers.
Example of Programming: test.a30
------------------------------------------------------------------
Line Number Source Line
2 macTEST .macro _a,_b,_c
3 .byte _a
4 .byte _b
5 .byte _c
6 .endm
7
8 macTEST 1,\\ ; Arguments of a macro call concatenated
9 2,\\
10 3
11 .byte err ; An error arises at this line
------------------------------------------------------------------
Example of an Error
test.a30 9 Error (asp308): Undefined symbol exist 'err'
- In the above example an error arises at source line number 11, but the error message says it is 9.
- 1.3 Workaround
- Refrain from concatenating arguments of macro calls.
- 1.4 Schedule of Fixing Problem
- We plan to fix this problem in our next release.
NC308WA, NC30WA, NC79WA, AS308, AS30, and AS79 Precautions
MESCT-NC308WA-001101D
- Problem on the Order of Searching Include Files
- 2.1 Versions Concerned
- Compiler for the M16C/80 series MCUs:
NC308WA V.3.00 Release 1--V.3.10 Release 3 (AS308 V.3.00 Release 1)
- Compiler for the M16C/60 and M16C/20 series MCUs:
NC30WA V.4.00 Release 1 (AS30 V.4.00 Release 1)
- Compiler for the 7900 series MCUs:
NC79WA V.4.00 Release 1 (AS79 V.4.00 Release 1)
- 2.2 Descriptions
- In the assemblers whose versions are concerned and later, include files are searched with reference to the directory where the assembler is invoked when the relative path is applied to operands of assembler directive ".include".
- [New Reference Directory] Directory where the assembler is invoked
- [Previous Reference Directory] Directory where the source file exists
- As a result of this change, such a symptom that include files cannot be found may appear even when a source file hitherto having no problem is assembled by any of the products concerned.
- 2.3 Workaround
- This problem can be circumvented in either of the following ways:
- (1) Change the relative path applied to operands of assembler directive ".include" for the reference directory of the relative path to be the directory where the assembler is invoked.
- (2) Change the directory where include files are saved for the reference directory of the relative path to be the directory where the assembler is invoked.
|
|
