On Tue, Apr 28, 2020 at 10:54 PM Sandra Loosemore
wrote:
>
> On 4/27/20 9:08 AM, Matthias Kretz wrote:
> >
> > @item -ffinite-math-only
> > @opindex ffinite-math-only
> > -Allow optimizations for floating-point arithmetic that assume
> > -that arguments and results are not NaNs or +-Infs.
> >
On 4/27/20 9:08 AM, Matthias Kretz wrote:
@item -ffinite-math-only
@opindex ffinite-math-only
-Allow optimizations for floating-point arithmetic that assume
-that arguments and results are not NaNs or +-Infs.
+Assume that floating-point types in the language do not have representations
for
On Tue, Apr 28, 2020 at 12:04 PM Richard Sandiford
wrote:
>
> Matthias Kretz writes:
> > On Dienstag, 28. April 2020 09:21:38 CEST Richard Biener wrote:
> >> On Mon, Apr 27, 2020 at 11:26 PM Matthias Kretz wrote:
> >> > * Why not disable NaN and Inf independently? Inf is just a reciprocal 0.
> >
Matthias Kretz writes:
> On Dienstag, 28. April 2020 09:21:38 CEST Richard Biener wrote:
>> On Mon, Apr 27, 2020 at 11:26 PM Matthias Kretz wrote:
>> > * Why not disable NaN and Inf independently? Inf is just a reciprocal 0.
>> > Inf is as far away from numeric_limits::max as 0 is from
>> > numer
On Tue, Apr 28, 2020 at 10:15 AM Matthias Kretz wrote:
>
> On Dienstag, 28. April 2020 09:21:38 CEST Richard Biener wrote:
> > On Mon, Apr 27, 2020 at 11:26 PM Matthias Kretz wrote:
> > > On Montag, 27. April 2020 21:39:17 CEST Richard Sandiford wrote:
> > > > "Dr. Matthias Kretz" writes:
> > >
On Dienstag, 28. April 2020 09:21:38 CEST Richard Biener wrote:
> On Mon, Apr 27, 2020 at 11:26 PM Matthias Kretz wrote:
> > On Montag, 27. April 2020 21:39:17 CEST Richard Sandiford wrote:
> > > "Dr. Matthias Kretz" writes:
> > > > On Montag, 27. April 2020 18:59:08 CEST Richard Sandiford wrote:
On Mon, Apr 27, 2020 at 11:26 PM Matthias Kretz wrote:
>
> On Montag, 27. April 2020 21:39:17 CEST Richard Sandiford wrote:
> > "Dr. Matthias Kretz" writes:
> > > On Montag, 27. April 2020 18:59:08 CEST Richard Sandiford wrote:
> > >> Richard Biener via Gcc-patches writes:
> > >> > On Mon, Apr 2
On Montag, 27. April 2020 21:39:17 CEST Richard Sandiford wrote:
> "Dr. Matthias Kretz" writes:
> > On Montag, 27. April 2020 18:59:08 CEST Richard Sandiford wrote:
> >> Richard Biener via Gcc-patches writes:
> >> > On Mon, Apr 27, 2020 at 6:09 PM Matthias Kretz wrote:
> >> >> Hi,
> >> >>
> >>
"Dr. Matthias Kretz" writes:
> On Montag, 27. April 2020 18:59:08 CEST Richard Sandiford wrote:
>> Richard Biener via Gcc-patches writes:
>> > On Mon, Apr 27, 2020 at 6:09 PM Matthias Kretz wrote:
>> >> Hi,
>> >>
>> >> This documentation change clarifies the effect of -ffinite-math-only.
>> >>
On Montag, 27. April 2020 18:59:08 CEST Richard Sandiford wrote:
> Richard Biener via Gcc-patches writes:
> > On Mon, Apr 27, 2020 at 6:09 PM Matthias Kretz wrote:
> >> Hi,
> >>
> >> This documentation change clarifies the effect of -ffinite-math-only.
> >> With the current documentation, it is
Richard Biener via Gcc-patches writes:
> On Mon, Apr 27, 2020 at 6:09 PM Matthias Kretz wrote:
>>
>> Hi,
>>
>> This documentation change clarifies the effect of -ffinite-math-only. With
>> the
>> current documentation, it is unclear what the presence of NaN and Inf
>> representations means if (a
On Mon, Apr 27, 2020 at 6:09 PM Matthias Kretz wrote:
>
> Hi,
>
> This documentation change clarifies the effect of -ffinite-math-only. With the
> current documentation, it is unclear what the presence of NaN and Inf
> representations means if (arithmetic) operations on such values are
> unspecifi
Hi,
This documentation change clarifies the effect of -ffinite-math-only. With the
current documentation, it is unclear what the presence of NaN and Inf
representations means if (arithmetic) operations on such values are
unspecified and even classification functions like isnan are unreliable. I
13 matches
Mail list logo
