public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/113295] [14 Regression] SPEC 2006 416.gamess miscompares on Aarch64 when built with -Ofast -march=native -flto
Date: Mon, 19 Feb 2024 13:13:01 +0000 [thread overview]
Message-ID: <bug-113295-4-98xe8lXFnH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113295-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113295
Tamar Christina <tnfchris at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2024-02-19
Ever confirmed|0 |1
Priority|P3 |P1
CC| |tnfchris at gcc dot gnu.org
--- Comment #1 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Ah, I missed this. Yeah we've seen it but didn't have time to track down untill
now.
however our CI shows it showed up between
g:ae034b9106fbdd855ec22ce221bb61a1a9a532c3 and
g:3333a064e4925afa1ad5f2f8c1350c4f57d631ce and
g:34d339bbd0c1f5b4ad9587e7ae8387c912cb028b is a target only change so unlikely
to be related.
bisecting.
next prev parent reply other threads:[~2024-02-19 13:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 17:42 [Bug target/113295] New: " jamborm at gcc dot gnu.org
2024-01-09 17:43 ` [Bug target/113295] [14 Regression] " pinskia at gcc dot gnu.org
2024-02-19 13:13 ` tnfchris at gcc dot gnu.org [this message]
2024-02-21 10:25 ` tnfchris at gcc dot gnu.org
2024-02-21 10:32 ` tnfchris at gcc dot gnu.org
2024-02-21 11:07 ` [Bug target/113295] [14 Regression] SPEC 2006 416.gamess miscompares on Aarch64 when built with -Ofast -mcpu=native since g:2f46e3578d45ff060a0a329cb39d4f52878f9d5a tnfchris at gcc dot gnu.org
2024-02-21 11:09 ` rsandifo at gcc dot gnu.org
2024-02-21 18:37 ` rsandifo at gcc dot gnu.org
2024-02-23 14:13 ` cvs-commit at gcc dot gnu.org
2024-02-23 14:13 ` cvs-commit at gcc dot gnu.org
2024-02-23 14:17 ` rsandifo 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-113295-4-98xe8lXFnH@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).