How to print this page

• With the IDE neglecting build error messages when a real-time OS is being used

1. Description
   Suppose you are making the build of a project that uses a real-time OS. 
   Even if the "Create Jump table" utility in the real-time OS outputs 
   any error or warning messages, High-performance Embedded Workshop does 
   not interpret these as errors or warnings. So these messages, when 
   displayed in the Output window, do not come with error or warning marks 
   and are not included in the error and warning count provided after the 
   build is complete.

2. Conditions
   This problem occurs if any one of the following combinations of a 
   compiler package and a real-time OS is used on High-performance 
   Embedded Workshop:
   (1) The C compiler package for the R32C/100 series V.1.01 Release 00 and 
       the real-time OS for the R32C series (M3T-MR100/4) V.1.00 Release 00
	   
   (2) Either of the C compiler packages for the M32C series (M3T-NC308WA) 
       V.5.41 Release 00 and V.5.41 Release 01, and 
       Any of the real-time OSes for the M32C series M3T-MR308 V.1.10 
       Release 1 through V.1.20 Release 1B or either of M3T-MR308/4 
       V.4.00 Release 00 and V.4.00 Release 01
	   
   (3) Any of the C compiler packages for the M16C series (M3T-NC30WA) 
       V.5.42 Release 00 through V.5.43 Release 00, and 
       Any of the real-time OSes for the M16C series M3T-MR30 V.3.10 
       Release 1 through V.3.30 Release 2 or M3T-MR30/4 V.4.00 Release 00

3. How to Check Error and Warning Messages
   The error and warning messages of the "Create Jump table" utility are 
   displayed just behind the first line of Linker Phase messages in the 
   Build tab in the Output window.
   So scroll the window to find top of Linker Phase messages and read them 
   to judge if they are error and warning messages.

4. Schedule of Fixing the Problem
   This problem is due to modules of the High-performance Embedded 
   Workshop included in each of the compiler packages involved.
   So we are fixing this problem in the next release of those compilers 
   by including the problem-fixed modules with their packages.