How to force gcc to report a warning/error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

We had an interesting error that was undetected in gcc:
{
  unsigned long a;
  unsigned long x=3;
  unsigned long y=4;
  a = 
      min(x,y);
}

I've simplified the example. In the original code, the contents of the min()
statement were longer, so that it was on a separate line from the assignment
operation.

Because of a bug, the assignment line was removed, and we had the following
code:
{
  unsigned long a;
  unsigned long x=3;
  unsigned long y=4;
      min(x,y);
}

Should this be picked up as a warning/error? 
Neither -Wall or -Wextra picked it up.

Many thanks,
Paul
-- 
View this message in context: http://old.nabble.com/How-to-force-gcc-to-report-a-warning-error-tp30055230p30055230.html
Sent from the gcc - Help mailing list archive at Nabble.com.



[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux