07.04.2013 Views

MPLAB C Compiler for PIC24 MCUs and dsPIC DSCs ... - Microchip

MPLAB C Compiler for PIC24 MCUs and dsPIC DSCs ... - Microchip

MPLAB C Compiler for PIC24 MCUs and dsPIC DSCs ... - Microchip

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

C.1 INTRODUCTION<br />

C.2 ERRORS<br />

<strong>MPLAB</strong> ® C COMPILER FOR<br />

<strong>PIC24</strong> <strong>MCUs</strong> AND <strong>dsPIC</strong> ® <strong>DSCs</strong><br />

USER’S GUIDE<br />

Appendix C. Diagnostics<br />

This appendix lists the most common diagnostic messages generated by the <strong>MPLAB</strong><br />

C <strong>Compiler</strong> <strong>for</strong> <strong>PIC24</strong> <strong>MCUs</strong> <strong>and</strong> <strong>dsPIC</strong> ® <strong>DSCs</strong> (<strong>for</strong>merly <strong>MPLAB</strong> C30).<br />

The compiler can produce two kinds of diagnostic messages: errors <strong>and</strong> warnings.<br />

Each kind has a different purpose.<br />

• Errors reports problems that make it impossible to compile your program. The<br />

compiler reports errors with the source file name <strong>and</strong> line number where the problem<br />

is apparent.<br />

• Warnings reports other unusual conditions in your code that may indicate a<br />

problem, although compilation can (<strong>and</strong> does) proceed. Warning messages also<br />

report the source file name <strong>and</strong> line number, but include the text warning: to distinguish<br />

them from error messages.<br />

Warnings may indicate danger points where you should check to make sure that your<br />

program really does what you intend; or the use of obsolete features; or the use of<br />

non-st<strong>and</strong>ard features of the compiler. Many warnings are issued only if you ask <strong>for</strong><br />

them, with one of the -W options (<strong>for</strong> instance,-Wall requests a variety of useful<br />

warnings).<br />

In rare instances, the compiler may issue an internal error message report. This<br />

signifies that the compiler itself has detected a fault that should be reported to<br />

<strong>Microchip</strong> support. Details on contacting support are contained elsewhere in this<br />

manual.<br />

Symbols<br />

\x used with no following HEX digits<br />

The escape sequence \x should be followed by hex digits.<br />

‘&’ constraint used with no register class<br />

The asm statement is invalid.<br />

‘%’ constraint used with last oper<strong>and</strong><br />

The asm statement is invalid.<br />

#elif after #else<br />

In a preprocessor conditional, the #else clause must appear after any #elif clauses.<br />

#elif without #if<br />

In a preprocessor conditional, the #if must be used be<strong>for</strong>e using the #elif.<br />

#else after #else<br />

In a preprocessor conditional, the #else clause must appear only once.<br />

#else without #if<br />

In a preprocessor conditional, the #if must be used be<strong>for</strong>e using the #else.<br />

© 2008 <strong>Microchip</strong> Technology Inc. DS51284H-page 163

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!