unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Romain GEISSLER via Libc-alpha <libc-alpha@sourceware.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: Many float/double errors in math/ testsuite with gcc master branch
Date: Wed, 30 Nov 2022 01:53:48 +0000	[thread overview]
Message-ID: <0A268E9F-8C53-4B59-8BAD-CCF11880800C@amadeus.com> (raw)
In-Reply-To: <CA+=Sn1m+Vfx79uG7ZdyZr_earX7BCDwaj3iGMx5XWzoyScjKsQ@mail.gmail.com>

Le 29 nov. 2022 à 04:38, Andrew Pinski <pinskia@gmail.com<mailto:pinskia@gmail.com>> a écrit :

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

Thanks,
Andrew Pinski

Hi,

Thanks for these pointers.

I tried to narrow a bit more today these regressions today. Most of them seems to have been introduced with the fixes for GCC bug 107569 (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107569 ).

However all the iseqsig tests seems to fail because of another reason, it was already failing with the gcc master branch of 15th of October, and I couldn’t test earlier commits as I had build failures. I have found GCC bug 106805  (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106805 ) which might be related.

Cheers,
Romain

  reply	other threads:[~2022-11-30  1:54 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
2022-11-30  1:53   ` Romain GEISSLER via Libc-alpha [this message]
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=0A268E9F-8C53-4B59-8BAD-CCF11880800C@amadeus.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).