From: Richard Earnshaw <rearnsha@arm.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard Earnshaw <rearnsha@arm.com>, christophe.lyon.oss@gmail.com
Subject: [committed v2 0/3] arm: fix problems when targetting extended FPUs [PR101723]
Date: Thu, 5 Aug 2021 12:57:47 +0100 [thread overview]
Message-ID: <20210805115750.3824520-1-rearnsha@arm.com> (raw)
Thanks, Christophe, I've updated the testsuite to fix all the issues I could
see from your test runs.
This is what I've finally committed, but if there's any more fallout, please
let me know.
R.
Richard Earnshaw (3):
arm: ensure the arch_name is always set for the build target
arm: Don't reconfigure globals in arm_configure_build_target
arm: reorder assembler architecture directives [PR101723]
gcc/config/arm/arm-c.c | 1 +
gcc/config/arm/arm-cpus.in | 1 +
gcc/config/arm/arm.c | 190 ++++++++----------
gcc/testsuite/gcc.target/arm/attr-neon.c | 9 +-
gcc/testsuite/gcc.target/arm/attr-neon2.c | 35 +++-
gcc/testsuite/gcc.target/arm/attr-neon3.c | 48 ++++-
.../arm/cortex-m55-nofp-flag-hard.c | 2 +-
.../arm/cortex-m55-nofp-flag-softfp.c | 2 +-
.../arm/cortex-m55-nofp-nomve-flag-softfp.c | 2 +-
.../gcc.target/arm/mve/intrinsics/mve_fpu1.c | 5 +-
.../gcc.target/arm/mve/intrinsics/mve_fpu2.c | 5 +-
gcc/testsuite/gcc.target/arm/pr69245.c | 6 +-
gcc/testsuite/gcc.target/arm/pr98636.c | 3 +-
.../gcc.target/arm/pragma_fpu_attribute.c | 7 +-
.../gcc.target/arm/pragma_fpu_attribute_2.c | 7 +-
15 files changed, 173 insertions(+), 150 deletions(-)
--
2.25.1
next reply other threads:[~2021-08-05 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-05 11:57 Richard Earnshaw [this message]
2021-08-05 11:57 ` [committed v2 1/3] arm: ensure the arch_name is always set for the build target Richard Earnshaw
2021-08-05 11:57 ` [committed v2 2/3] arm: Don't reconfigure globals in arm_configure_build_target Richard Earnshaw
2021-08-05 11:57 ` [committed v2 3/3] arm: reorder assembler architecture directives [PR101723] Richard Earnshaw
2021-08-06 14:08 ` Christophe Lyon
2021-08-06 14:21 ` Christophe Lyon
2021-08-06 14:28 ` Richard Earnshaw
2021-08-06 14:43 ` Christophe Lyon
2021-08-06 14:25 ` Richard Earnshaw
2021-08-09 17:47 ` Christophe Lyon
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=20210805115750.3824520-1-rearnsha@arm.com \
--to=rearnsha@arm.com \
--cc=christophe.lyon.oss@gmail.com \
--cc=gcc-patches@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).