|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: Format security warnings now in GCC
From: Chris Evans (chris
scary.beasts.org)Date: Thu Dec 07 2000 - 05:47:28 CST
- Next message: Joseph S. Myers: "Re: Format security warnings now in GCC"
- Previous message: Joseph S. Myers: "Format security warnings now in GCC"
- In reply to: Joseph S. Myers: "Format security warnings now in GCC"
- Next in thread: Joseph S. Myers: "Re: Format security warnings now in GCC"
- Reply: Chris Evans: "Re: Format security warnings now in GCC"
- Reply: Joseph S. Myers: "Re: Format security warnings now in GCC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, 7 Dec 2000, Joseph S. Myers wrote:
> I've finally managed to get format security warnings accepted into GCC.
[...]
Nice one Joseph!
Still on the security/gcc side of things, any chance you could whine at
the right people to get -Wconversion fixed?
Currently, this produces a warning:
void somefunc(unsigned int arg);
...
{
int i = -1;
somefunc(i); <--- warning due to signed/unsigned conversion
}
This however does not, despite being the same conversion:
{
int i = -1;
unsigned int j = i; <--- no warning
}
Cheers
Chris
- Next message: Joseph S. Myers: "Re: Format security warnings now in GCC"
- Previous message: Joseph S. Myers: "Format security warnings now in GCC"
- In reply to: Joseph S. Myers: "Format security warnings now in GCC"
- Next in thread: Joseph S. Myers: "Re: Format security warnings now in GCC"
- Reply: Chris Evans: "Re: Format security warnings now in GCC"
- Reply: Joseph S. Myers: "Re: Format security warnings now in GCC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]