SW006015 Microchip Technology, SW006015 Datasheet - Page 27

• Manufacturer Part Number: SW006015
• Description: C COMPILER MPLAB C32
• Manufacturer: Microchip Technology
• Type: Compilerr
• Series: PIC32r

Specifications of SW006015

• Supported Families: PIC32MX5, MX6, And MX7
• Core Architecture: PIC
• Kit Contents: Software And Docs
• Mcu Supported Families: PIC32 MCUs
• Tool Function: Compiler
• Supported Devices: PIC32 MCUs
• Tool Type: Compiler
• Processor Series: PIC32
• Lead Free Status / RoHS Status: Not applicable / Not applicable
• For Use With/related Products: PIC32
• Lead Free Status / Rohs Status: Lead free / RoHS Compliant

© 2007 Microchip Technology Inc.
The following -W options are not implied by -Wall. Some of them warn about
constructions that users generally do not consider questionable, but which you might
occasionally wish to check for. Others warn about constructions that are necessary or
hard to avoid in some cases, and there is no simple way to modify the code to suppress
the warning.
TABLE 1-6:
-W
-Waggregate-return
-Wbad-function-cast
Option
WARNING AND ERROR OPTIONS NOT IMPLIED BY
-WALL
Print extra warning messages for these events:
• A nonvolatile automatic variable might be changed by a
• A function could exit both via return value; and
• An expression-statement or the left-hand side of a
• An unsigned value is compared against zero with < or <=.
• A comparison like x<=y<=z appears, This is equivalent
• Storage-class specifiers like static are not the first
• If -Wall or -Wunused is also specified, warn about
• A comparison between signed and unsigned values could
• An aggregate has a partly bracketed initializer. For
• An aggregate has an initializer that does not initialize all
Warn if any functions that return structures or unions are
defined or called.
Warn whenever a function call is cast to a non-matching type.
For example, warn if int foof() is cast to anything *.
call to longjmp. These warnings are possible only in
optimizing compilation. The compiler sees only the calls
to setjmp. It cannot know where longjmp will be called.
In fact, a signal handler could call it at any point in the
code. As a result, a warning may be generated even
when there is in fact no problem, because longjmp
cannot in fact be called at the place that would cause a
problem.
return;. Completing the function body without passing
any return statement is treated as return;.
comma expression contains no side effects. To suppress
the warning, cast the unused expression to void. For
example, an expression such as x[i,j] causes a
warning, but x[(void)i,j] does not.
to (x<=y ? 1 : 0) <= z, which is a different
interpretation from that of ordinary mathematical notation.
things in a declaration. According to the C Standard, this
usage is obsolescent.
unused arguments.
produce an incorrect result when the signed value is
converted to unsigned. (But don’t warn if
-Wno-sign-compare is also specified.)
example, the following code would evoke such a warning,
because braces are missing around the initializer for
x.h:
struct s { int f, g; };
struct t { struct s h; int i; };
struct t x = { 1, 2, 3 };
members. For example, the following code would cause
such a warning, because x.h would be implicitly
initialized to zero:
struct s { int f, g, h; };
struct s x = { 3, 4 };
Definition
DS51686A-page 23