------- Comment #4 from felix-gcc at fefe dot de 2007-01-15 19:57 -------
(In reply to comment #2)
> signed type overflow is undefined by the C standard, use unsigned int for the
> addition or use -fwrapv.
You have GOT to be kidding?
All kinds of security issues are caused by integer wraps, and you are just
telling me that with gcc 4.1 and up I cannot test for them for signed data
types any more?!
You are missing the point here. There HAS to be a way to get around this.
Existing software uses signed int and I can't just change it to unsigned int,
but I still must be able to check for a wrap! There does not appear to be a
work around I could do in the source code either! Do you expect me to cast it
to unsigned, shift right by one, and then add or what?!
PLEASE REVERT THIS CHANGE. This will create MAJOR SECURITY ISSUES in ALL
MANNER OF CODE. I don't care if your language lawyers tell you gcc is right.
THIS WILL CAUSE PEOPLE TO GET HACKED.
I found this because one check to prevent people from getting hacked failed.
THIS IS NOT A JOKE. FIX THIS! NOW!
--
felix-gcc at fefe dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475
