You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to use __builtin_add_overflow and the likes, one has to introduce additional objects the address of which can be taken. To avoid such overhead when building goto programs directly, it would be desirable to have variants of the overflow intrinsics that take lvalues as (optional) parameters so that both is-there-an-overflow and the actual value can be assigned in a single instruction.
The text was updated successfully, but these errors were encountered:
Doing both the arithmetic operation and determining whether or not there
was an overflow previously required either multiple expressions or going
via `__builtin_X_overflow`, which should be specific to the C front-end.
The new expression returns a struct with two components, the first of
which has the type of the arithmetic operation, and the second is
Boolean.
Fixes: diffblue#6841
Doing both the arithmetic operation and determining whether or not there
was an overflow previously required either multiple expressions or going
via `__builtin_X_overflow`, which should be specific to the C front-end.
The new expression returns a struct with two components, the first of
which has the type of the arithmetic operation, and the second is
Boolean.
Fixes: diffblue#6841
Doing both the arithmetic operation and determining whether or not there
was an overflow previously required either multiple expressions or going
via `__builtin_X_overflow`, which should be specific to the C front-end.
The new expression returns a struct with two components, the first of
which has the type of the arithmetic operation, and the second is
Boolean.
Fixes: diffblue#6841
In order to use
__builtin_add_overflow
and the likes, one has to introduce additional objects the address of which can be taken. To avoid such overhead when building goto programs directly, it would be desirable to have variants of the overflow intrinsics that take lvalues as (optional) parameters so that both is-there-an-overflow and the actual value can be assigned in a single instruction.The text was updated successfully, but these errors were encountered: