public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/106574] gcc 12 with O3 leads to failures in glibc's y1f128 tests
Date: Wed, 10 Aug 2022 07:25:21 +0000	[thread overview]
Message-ID: <bug-106574-4-IpNOy3tb5j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106574-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106574

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Michael Hudson-Doyle from comment #3)
> Certainly this could be "handled" by bumping the tolerance I guess. Not sure
> how to tell if that is appropriate though...

You have to look what GCC actually does, like if it is constant folding as
suggested or sth else.

  parent reply	other threads:[~2022-08-10  7:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-09 22:54 [Bug c/106574] New: " michael.hudson at canonical dot com
2022-08-09 23:12 ` [Bug target/106574] " michael.hudson at canonical dot com
2022-08-09 23:15 ` pinskia at gcc dot gnu.org
2022-08-09 23:18 ` michael.hudson at canonical dot com
2022-08-10  7:25 ` rguenth at gcc dot gnu.org [this message]
2022-08-10 14:58 ` joseph at codesourcery dot com
2022-08-10 21:26 ` michael.hudson at canonical dot com
2022-08-10 22:25 ` joseph at codesourcery dot com
2022-08-10 22:49 ` michael.hudson at canonical dot com
2022-08-10 22:54 ` michael.hudson at canonical dot com
2022-08-10 23:27 ` michael.hudson at canonical dot com
2022-08-11 20:34 ` joseph at codesourcery dot com
2022-08-11 21:36 ` michael.hudson at canonical dot com
2022-09-06 22:07 ` michael.hudson at canonical dot com
2022-09-06 22:14 ` pinskia at gcc dot gnu.org

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=bug-106574-4-IpNOy3tb5j@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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: 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).