 |
|
|
MAEC TOOL NEWS:
MAECT-M3T-NC308WA_1-020916D
Notes on C Compilers
M3T-NC308WA, M3T-NC30WA, and M3T-NC79WA;
and Assemblers AS308, AS30, and AS79
|
|---|
Please take note of the following problems in using C compilers (with an assembler and integrated development environment) M3T-NC308WA, M3T-NC30WA, and M3T-NC79WA:
- On using command option "-O" in the load-module converter
- On an "IF-ELIF-ENDIF" construct in structured description
- Problem on Using Command Option "-O" in the Load-Module Converter
- 1.1 Products and Versions Concerned
- C compilers:
- M3T-NC308WA V.1.00 Release 1 -- V.5.00 Release 1 for the M32C/80 and M16C/80 series of MCUs
- M3T-NC30WA V.3.00 Release 1 -- V.5.00 Release 2 for the M16C/60, M16C/30, M16C/20, and M16C/10 series of MCUs
- M3T-NC79WA V.2.00 Release 1 -- V.4.10 Release 1 for the 79xx series of MCUs
- Relocatable assemblers:
- AS308 V.1.00 Release 1 -- V.2.00 Release 1 for the M32C/80 and M16C/80 series of MCUs
- AS30 V.1.00 Release 1 -- V.3.20 Release 1 for the M16C/60, M16C/30, M16C/20, and M16C/10 series of MCUs
- AS79 V.1.00 Release 1 -- V.3.20 Release 1 for the 79xx series of MCUs
- 1.2 Description
- When command option "-O" is used to specify the name of an output file, the file may be generated without its filename extension if a period ( . ) is contained in the filename (including its path).
- 1.3 Example
--------------------------------------------------------------------
> lmc308 -o ..\output\sample sample.x30
--------------------------------------------------------------------
- In this example, the output file will be generated with the name "sample", not the correct name "sample.mot".
- 1.4 Workaround
- If you specify an output file with a period ( . ) being contained in the filename (including its path), append filename extension ".mot" or ".hex" to the filename.
[Example]
--------------------------------------------------------------------
> lmc308 -o ..\output\sample.mot sample.x30 ; .mot is appended.
--------------------------------------------------------------------
- 1.5 Schedule of Fixing the problem
- We plan to fix this problem in our next release.
Notes on C Compilers M3T-NC308WA, M3T-NC30WA, and M3T-NC79WA; and Assemblers AS308, AS30, and AS79
MAECT-M3T-NC308WA_1-020916D
- Problem on an "IF-ELIF-ENDIF" Construct in Structured Description
- 2.1 Products and Versions Concerned
- C compilers:
- M3T-NC308WA V.1.00 Release 1 -- V.5.00 Release 1 for the M32C/80 and M16C/80 series of MCUs
- M3T-NC30WA V.3.00 Release 1 -- V.5.00 Release 2 for the M16C/60, M16C/30, M16C/20, and M16C/10 series of MCUs
- Relocatable assemblers:
- AS308 V.1.00 Release 1 -- V.2.00 Release 1 for the M32C/80 and M16C/80 series of MCUs
- AS30 V.1.00 Release 1 -- V.3.20 Release 1 for the M16C/60, M16C/30, M16C/20, and M16C/10 series of MCUs
- 2.2 Description
- When the conditional expressions in "IF" and "ELIF" statements contain logical ORs ("||") in an "IF-ELIF-ENDIF" construct written in structured description, an error message, "Symbol was already defined as the same type", is unnecessarily displayed.
- 2.3 Example
--------------------------------------------------------------------
IF [sym1] == 1 || [sym2] == 2 ;(1)
: Program statement
ELIF [sym1] == 3 || [sym2] == 4 ;(2)
: Program statement
ELSE
: Program statement
ENDIF
--------------------------------------------------------------------
- In this example, an error message will unnecessarily be displayed for statement (2).
- 2.4 Workaround
- When the conditional expressions in "IF" and "ELIF" statements contain logical ORs ("||") in an "IF-ELIF-ENDIF" construct in structured description, substitute "ELSE" for "ELIF" and describe the conditional expression in the original "ELIF" in "IF" format into the program statement of the substituted "ELSE".
[Example]
--------------------------------------------------------------------
IF [sym1] == 1 || [sym2] == 2
: Program statement
ELSE ; Substituted for ELIF.
IF [sym1] == 3 || [sym2] == 4
; Original ELIF's conditional statement
; described in IF format
: Program statement
ELSE
: Program statement
ENDIF
ENDIF
--------------------------------------------------------------------
- 2.5 Schedule of Fixing the Problem
- We plan to fix this problem in our next release.
|
|
