public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] i386: Regenerate ulps Date: Tue, 26 Apr 2022 15:01:46 +0000 (GMT) [thread overview] Message-ID: <20220426150146.4DDB0385842B@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=e465d97653311c3687aee49de782177353acfe86 commit e465d97653311c3687aee49de782177353acfe86 Author: Carlos O'Donell <carlos@redhat.com> Date: Tue Apr 26 10:52:41 2022 -0400 i386: Regenerate ulps These failures were caught while building glibc master for Fedora Rawhide which is built with '-mtune=generic -msse2 -mfpmath=sse' using gcc 11.3 (gcc-11.3.1-2.fc35) on a Cascadelake Intel Xeon processor. Diff: --- sysdeps/i386/fpu/libm-test-ulps | 2 +- sysdeps/i386/i686/fpu/multiarch/libm-test-ulps | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/sysdeps/i386/fpu/libm-test-ulps b/sysdeps/i386/fpu/libm-test-ulps index 7601049110..84e6686eba 100644 --- a/sysdeps/i386/fpu/libm-test-ulps +++ b/sysdeps/i386/fpu/libm-test-ulps @@ -668,7 +668,7 @@ ldouble: 4 Function: Imaginary part of "clog10": double: 2 -float: 1 +float: 2 float128: 2 ldouble: 2 diff --git a/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps b/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps index a39c89cec1..cc21e6907f 100644 --- a/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps +++ b/sysdeps/i386/i686/fpu/multiarch/libm-test-ulps @@ -668,7 +668,7 @@ ldouble: 4 Function: Imaginary part of "clog10": double: 2 -float: 1 +float: 2 float128: 2 ldouble: 2
next reply other threads:[~2022-04-26 15:01 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-26 15:01 Carlos O'Donell [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-07-25 20:31 Arjun Shankar 2021-03-02 14:43 Florian Weimer 2020-12-21 17:19 Florian Weimer
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=20220426150146.4DDB0385842B@sourceware.org \ --to=carlos@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).