From: Carlos O'Donell <carlos@redhat.com>
To: Tulio Magno Quites Machado Filho <tuliom@linux.ibm.com>,
Joseph Myers <joseph@codesourcery.com>,
Matheus Castanho <msc@linux.ibm.com>
Cc: patsy@redhat.com, libc-alpha@sourceware.org
Subject: Re: [PATCH v2] powerpc: Update ULPs and output for j0 with ibm128
Date: Thu, 10 Sep 2020 13:08:28 -0400 [thread overview]
Message-ID: <ea48a1c1-52ad-2d85-378d-58fc06d56d93@redhat.com> (raw)
In-Reply-To: <87een93g2f.fsf@linux.ibm.com>
On 9/10/20 9:40 AM, Tulio Magno Quites Machado Filho wrote:
> Joseph Myers <joseph@codesourcery.com> writes:
>
>> On Wed, 9 Sep 2020, Matheus Castanho wrote:
>>
>>> Instead of updating the ldouble ULPs for j0 with an upstream GCC,
>>> constantly increasing their values, this patch regenerates them with a
>>> GCC compiled with the patch mentioned above. This way we have the actual
>>> precise ULPs listed in libm-test-ulps. Of course, when compiling with
>>> an upstream compiler some tests will fail as the calculated ULPs will be
>>> higher than the expected ones. For such tests, we mark the
>>> corresponding entries in math/auto-libm-test-in with
>>> xfail-rounding:ibm128-libgcc.
>>
>> xfail-rounding:ibm128-libgcc is intended for the sort of edge cases where
>> upstream GCC produces results that are wildly off. It's not intended for
>> these sorts of cases where it gives slightly bigger ulps that are still
>> within the accepted bounds.
>
> Carlos, Joseph,
>
> I'm afraid that Matheus is either in a deadlock or we need a clearer
> explanation of what is acceptable for ibm128.
>
> Notice that Matheus' first patch was rejected because results were greater
> than 9.
It was later shown to me that >9 ULPs was acceptable for ibm128, my apologies
for not being clearer that I was withdrawing my objection.
> With that said, would both of you accept the first version of this patch?
> https://patchwork.sourceware.org/project/glibc/patch/20200820183700.115087-1-msc@linux.ibm.com/
Yes.
Patsy Griffin from my team also suggested this on September 2nd, she
is seeing these failures in our own testing. It would be good to have
them resolved.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-09-10 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 16:58 Matheus Castanho
2020-09-09 17:17 ` Joseph Myers
2020-09-10 13:40 ` Tulio Magno Quites Machado Filho
2020-09-10 15:07 ` Joseph Myers
2020-09-10 18:52 ` Tulio Magno Quites Machado Filho
2020-09-10 17:08 ` Carlos O'Donell [this message]
2020-09-10 17:29 ` Matheus Castanho
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=ea48a1c1-52ad-2d85-378d-58fc06d56d93@redhat.com \
--to=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=msc@linux.ibm.com \
--cc=patsy@redhat.com \
--cc=tuliom@linux.ibm.com \
/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).