This release note describes the new M16C v3.1r1 toolchain.
The M16C toolchain v3.1 consists of a full embedded development toolchain, supporting:
Renesas M16C/10, M16C/20, M16C/Tiny, M16C/30, M16C/60 and R8C/tiny series of microprocessors.
ISO C99, ANSI C90, MISRA C, C++, EC++ and assembly language, with M16C specific extensions.
M16C/R8C development boards from Renesas, Glyn and Oaks.
Debugging in the CrossView Pro source level debugger, using the M16C/R8C simulator, TASKING rom monitor.
The highlights of this release are:
New runtime erorr checking facilities.
New profiling facilities.
Support for MISRA-C 2004.
Improved speed of the toolchain.
Solving of reported problems. See solved_known_problems_v3.1r1.htm.
The TASKING C compiler now supports a number of runtime error checks. When a check is enabled, the compiler adds code to reveal run-time errors. Library routines show descriptive errors if a check fails.
| Runtime error checks | |
|---|---|
| bounds | Checks before every pointer update and pointer dereference that it points to a valid object, be it in global memory, on the stack or on the heap. |
| case | Checks in a switch statement that a case value is not unhandled. |
| malloc | Checks every malloc() and free() call for validity. |
| stack | Checks for every function and for every variable length array that it does not run off the stack. |
| division by zero | Checks before every division that the denominator is valid. |
The TASKING M16C toolchain can now generate profile reports. Profiling instrumentation added by the compiler will update performance counters. After a program has run, a runtime report will be generated. The EDE can present these profiling numbers in a flexible way.
The compiler can generate instrumentation counters for a call graph, function entry, function timers and for every basic block.
The Motor Industry Software Reliability Association (MISRA) has released a new version of it's MISRA-C:2004. The number of supported MISRA-C code checking rules has been increased from 117 to 122. As before, you can specify in the EDE which rules should be checked, and the linker can generate a report of compliance for all linked in modules.
Building an application has become much faster in v3.1r1 compared to v3.0r1. The compilation time has improved and the assembler did have a complete overhaule.
To obtain a license file, please contact your local sales / support center:
http://www.tasking.com/about/contacts/.
Please use the EDE "Prepare an E-mail" item on the Help - Technical Support menu to report problems with this product.
Visit website http://www.tasking.com/support/m16c/ to get the latest news about this product.
TASKING M16C Support web site
TASKING M16C Product Page
TASKING Home Page
TASKING Developers' Forum