From: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: libc-alpha@sourceware.org, fweimer@redhat.com, carlos@redhat.com
Subject: Re: [PATCH] Add XFAIL_ROUNDING_IBM128_LIBGCC to more fma() tests
Date: Tue, 15 Jan 2019 18:55:00 -0000 [thread overview]
Message-ID: <87zhs14up4.fsf@linux.ibm.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1901142133121.18054@digraph.polyomino.org.uk>
Joseph Myers <joseph@codesourcery.com> writes:
> On Mon, 14 Jan 2019, Tulio Magno Quites Machado Filho wrote:
>
>> Contrary to what I had thought: this is indeed caused by spurious
>> overflows from libgcc (confirmed with the patch applied to libgcc).
>> We can suppress the all errors with XFAIL_ROUNDING_IBM128_LIBGCC.
>
> In that case - if it's only an issue in non-default rounding modes - this
> patch is OK.
They appear only when rounding upward and downward.
Pushed as ecdacd34a2ac3b6d5a529ff218b29261d9d98a7a.
Thanks!
--
Tulio Magno
next prev parent reply other threads:[~2019-01-15 18:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 22:01 [PATCH] Fix ldbl-128ibm fma (Inf, Inf, finite) (bug 23272) Tulio Magno Quites Machado Filho
2018-06-13 23:07 ` Joseph Myers
2018-09-21 12:00 ` Florian Weimer
2018-09-21 12:46 ` Joseph Myers
2018-09-21 12:51 ` Florian Weimer
2018-09-21 17:27 ` Tulio Magno Quites Machado Filho
2019-01-14 20:10 ` [PATCH] Add XFAIL_ROUNDING_IBM128_LIBGCC to more fma() tests Tulio Magno Quites Machado Filho
2019-01-14 21:33 ` Joseph Myers
2019-01-15 18:55 ` Tulio Magno Quites Machado Filho [this message]
2019-01-15 20:53 ` Joseph Myers
2019-01-16 12:44 ` Tulio Magno Quites Machado Filho
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zhs14up4.fsf@linux.ibm.com \
--to=tuliom@linux.ibm.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).