This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC optimization bug?


Can someone elaborate what -fno-strict-overflow is supposed to do and how it differs from -fwrapv? Since the documentation says that with -fstrict-overflow overflow with signed numbers is undefined, wouldn't that make overflow with signed numbers *not* undefined with -fno-strict-overflow?

On Tuesday 17 January 2017 04:19 PM, Mason wrote:
-fstrict-overflow
>
>Allow the compiler to assume strict signed overflow rules, depending
>on the language being compiled. For C (and C++) this means that
>overflow when doing arithmetic with signed numbers is undefined,
>which means that the compiler may assume that it does not happen.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]