public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Tom Coldrick <thomas.coldrick@codethink.co.uk>,
	libc-alpha@sourceware.org
Subject: Re: [PATCH] manual: Avoid name collision in libm ULP table [BZ #28956]
Date: Mon, 11 Apr 2022 11:46:45 -0400	[thread overview]
Message-ID: <334b46e3-7ffa-7fef-922b-f4a304f3616f@redhat.com> (raw)
In-Reply-To: <dcb83c75-23d0-26a5-0c63-c4735c275dfa@linaro.org>

On 4/5/22 07:16, Adhemerval Zanella via Libc-alpha wrote:
> 
> 
> On 05/04/2022 06:46, Tom Coldrick via Libc-alpha wrote:
>> The 32-bit and 64-bit variants of RISC-V share the same name - "RISC-V"
>> - when generating the libm error table for the info pages. This
>> collision, and the way how the table is generated, mean that the values
>> in the final table for "RISC-V" may be either for the 32- or 64-bit
>> variant, with no indication as to which.
>>
>> As an additional side-effect, this makes the build non-reproducible, as
>> the error table generated is dependent upon the host filesystem
>> implementation.
>>
>> To solve this issue, the libm-test-ulps-name files for both variants
>> have been modified to include their word size, so as to remove the
>> collision and provide more accurate information in the table.
>>
>> An alternative proposed was to merge the two variants' ULP values into a
>> single file, but this would mean that information about error values is
>> lost, as the two variants are not identical. Some differences are
>> considerable, notably the values for the exp() function are large.
> 
> Path looks ok, but is there any expectation that RV64 and RV32 hardware
> floating-point implementation or compiler generate code to have different
> precision? Otherwise it would be simple to just use one ulp tests file.

That is a good question, but it could be handled with a distinct patch to remove the files
if the maintainers consider that the right direction to take.

Overall this patch looks correct to me also and I've pushed it as trivial in that it makes
the manual more correct.

I tested the patch on x86_64 with make pdf and the table looks good and disambiguates the
results.

Reviewed-by: Carlos O'Donell <carlos@redhat.com>
Tested-by: Carlos O'Donell <carlos@redhat.com>

-- 
Cheers,
Carlos.


  reply	other threads:[~2022-04-11 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-05  9:46 Tom Coldrick
2022-04-05 11:16 ` Adhemerval Zanella
2022-04-11 15:46   ` Carlos O'Donell [this message]
2022-04-05 13:29 ` Florian Weimer
2022-04-05 15:25   ` Andreas Schwab

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=334b46e3-7ffa-7fef-922b-f4a304f3616f@redhat.com \
    --to=carlos@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=libc-alpha@sourceware.org \
    --cc=thomas.coldrick@codethink.co.uk \
    /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).