public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/113611] [14 Regression] gcc.dg/pr110279-1.c fails on cross build since gcc-14-5779-g746344dd538
Date: Tue, 05 Mar 2024 16:48:56 +0000 [thread overview]
Message-ID: <bug-113611-4-HUbkYI3Upo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113611-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113611
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
I don't see how this can be a regression.
> --with-fpu=vfpv3-d16
FMA was added in vfpv4. If I change the fpu to add this then the test
generates the relevant comments in the dump file.
Arguably this test should check that the target has FMA instructions before
running, but that's a different issue.
prev parent reply other threads:[~2024-03-05 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 4:29 [Bug target/113611] New: " thiago.bauermann at linaro dot org
2024-01-26 4:32 ` [Bug testsuite/113611] " pinskia at gcc dot gnu.org
2024-01-31 14:33 ` rguenth at gcc dot gnu.org
2024-03-05 16:48 ` rearnsha at gcc dot gnu.org [this message]
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-113611-4-HUbkYI3Upo@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).