On Tue, 28 Sep 2021, Roger Sayle wrote:
> Next, I'd like to state that your "five restrictions" ontology is an
> excellent starting point, but I'd like to argue that your proposed list
> of 5 is the wrong shape (insufficiently refined). Instead, I'd like to
> counter-propose that an improvement
ING_MATH_INEXACT)
> double x = 2.0/3.0;
> double y = 2.0/3.0;
> we may even wish to perfom the division twice (c.f. your restriction [2]).
>
>
> I hope this is useful/insightful. Please let me know if you strongly feel
> all FP traps
> must be treated the same by
me know if you strongly feel
all FP traps
must be treated the same by the middle-end. Indeed, if flag_trapping_math
is
restricted to only be FLAG_TRAPPING_DEFAULT in a front-end(s), they will be.
Best regards,
Roger
--
-Original Message-
From: Joseph Myers
Sent: 27 September 2021 21:05
On Sat, 25 Sep 2021, Roger Sayle wrote:
> Normally Boolean options/flags in GCC take the values zero or one.
> This patch tweaks flag_trapping_math to take the values 0 or 65535.
> More accurately it introduces a new trapping_math_model enumeration in
> flag-types.h, and uses this to allow front-e
