https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102317
--- Comment #12 from qinzhao at gcc dot gnu.org --- (In reply to Kees Cook from comment #11) > The trouble with "optimize" is that it just doesn't work. The kernel has > banned its use because it results in all other optimization options being > forgotten for the function in question. How about Jacub's another suggestion in comment#10: "If you don't want to use optimize attribute, there is always the option to just do the arithmetics in unsigned types in the few selected functions where you don't want the sanitization"? is it possible to use "unsigned" integer instead of "signed" integer for the cases you want the "wrap around" behavior when overflow? if not, what's the major issue with this workaround?
