unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Pinski via Libc-alpha <libc-alpha@sourceware.org>
To: Romain GEISSLER <romain.geissler@amadeus.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: Many float/double errors in math/ testsuite with gcc master branch
Date: Mon, 28 Nov 2022 19:38:32 -0800	[thread overview]
Message-ID: <CA+=Sn1m+Vfx79uG7ZdyZr_earX7BCDwaj3iGMx5XWzoyScjKsQ@mail.gmail.com> (raw)
In-Reply-To: <4872FA2D-6165-48DE-B06C-98AE3E788A14@amadeus.com>

On Mon, Nov 28, 2022 at 5:26 PM Romain GEISSLER via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Hi,
>
> Trying to build currently a toolchain using glibc (current master branch) + gcc (current master branch) + binutils (release branch 2.39) on Linux x86_64 yields for me 53 test failure in the math/ folder. You can find the list of these tests at the end of this mail. Trying to downgrade to the latest commit of the current release branch of gcc 12 (so gcc 12.2.1) make all my glibc test failure disappear. Checking randomly couple of the .out files of the failing tests, it seems these test don’t work at all with gcc 13, there are many errors, and it doesn’t seem it’s due to a small change of precision. Am I the only one to experiences these test failure ? In case you don’t have such errors in the same conditions, how shall I report these errors for investigation ? Just the .out file would be enough ? I don’t know anything about these math/ tests, it’s the first time I see them failing like this.

This might be GCC bug 107879 (https://gcc.gnu.org/PR107879 ) or GCC
bug 107608 (https://gcc.gnu.org/PR107608 ) . I am suspecting the first
one. Jakub has a fix which he is I suspect will be submitting tomorrow
too.

Thanks,
Andrew Pinski

>
> Cheers,
> Romain
>
> FAIL: math/test-double-cosh
> FAIL: math/test-double-exp10
> FAIL: math/test-double-expm1
> FAIL: math/test-double-iseqsig
> FAIL: math/test-double-lgamma
> FAIL: math/test-double-log1p
> FAIL: math/test-double-tgamma
> FAIL: math/test-float-cosh
> FAIL: math/test-float-expm1
> FAIL: math/test-float-iseqsig
> FAIL: math/test-float-lgamma
> FAIL: math/test-float-log1p
> FAIL: math/test-float-tgamma
> FAIL: math/test-float128-catan
> FAIL: math/test-float128-catanh
> FAIL: math/test-float128-cosh
> FAIL: math/test-float128-exp10
> FAIL: math/test-float128-iseqsig
> FAIL: math/test-float128-lgamma
> FAIL: math/test-float128-log
> FAIL: math/test-float128-log1p
> FAIL: math/test-float128-pow
> FAIL: math/test-float128-tgamma
> FAIL: math/test-float128-y0
> FAIL: math/test-float128-y1
> FAIL: math/test-float32-cosh
> FAIL: math/test-float32-expm1
> FAIL: math/test-float32-iseqsig
> FAIL: math/test-float32-lgamma
> FAIL: math/test-float32-log1p
> FAIL: math/test-float32-tgamma
> FAIL: math/test-float32x-cosh
> FAIL: math/test-float32x-exp10
> FAIL: math/test-float32x-expm1
> FAIL: math/test-float32x-iseqsig
> FAIL: math/test-float32x-lgamma
> FAIL: math/test-float32x-log1p
> FAIL: math/test-float32x-tgamma
> FAIL: math/test-float64-cosh
> FAIL: math/test-float64-exp10
> FAIL: math/test-float64-expm1
> FAIL: math/test-float64-iseqsig
> FAIL: math/test-float64-lgamma
> FAIL: math/test-float64-log1p
> FAIL: math/test-float64-tgamma
> FAIL: math/test-float64x-cosh
> FAIL: math/test-float64x-iseqsig
> FAIL: math/test-float64x-lgamma
> FAIL: math/test-float64x-tgamma
> FAIL: math/test-ldouble-cosh
> FAIL: math/test-ldouble-iseqsig
> FAIL: math/test-ldouble-lgamma
> FAIL: math/test-ldouble-tgamma

  parent reply	other threads:[~2022-11-29  3:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-29  1:22 Many float/double errors in math/ testsuite with gcc master branch Romain GEISSLER via Libc-alpha
2022-11-29  2:09 ` Joseph Myers
2022-11-29  3:38 ` Andrew Pinski via Libc-alpha [this message]
2022-11-30  1:53   ` Romain GEISSLER via Libc-alpha
2022-11-30 19:12     ` Joseph Myers

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+=Sn1m+Vfx79uG7ZdyZr_earX7BCDwaj3iGMx5XWzoyScjKsQ@mail.gmail.com' \
    --to=libc-alpha@sourceware.org \
    --cc=pinskia@gmail.com \
    --cc=romain.geissler@amadeus.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).