From: Christophe Lyon <christophe.lyon@linaro.org>
To: gcc Patches <gcc-patches@gcc.gnu.org>
Subject: testsuite: gcc.c-torture/execute/ieee/cdivchkld.c needs fmaxl
Date: Tue, 4 May 2021 22:57:39 +0200 [thread overview]
Message-ID: <CAKdteObK-TT06PrFHwHxFDZ39qdzi2tcjnm2R6qboD7PuP9qxg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 716 bytes --]
The new test gcc.c-torture/execute/ieee/cdivchkld.c needs fmaxl(),
which may not be available, for instance on aarch64-elf with newlib.
As discussed in the PR, requiring c99_runtime enables to skip the test
in this case.
2021-05-04 Christophe Lyon <christophe.lyon@linaro.org>
PR testsuite/100355
gcc/testsuite/
* gcc.c-torture/execute/ieee/cdivchkld.x: New.
diff --git a/gcc/testsuite/gcc.c-torture/execute/ieee/cdivchkld.x
b/gcc/testsuite/gcc.c-torture/execute/ieee/cdivchkld.x
new file mode 100644
index 0000000..f798152
--- /dev/null
+++ b/gcc/testsuite/gcc.c-torture/execute/ieee/cdivchkld.x
@@ -0,0 +1,4 @@
+if { [check_effective_target_c99_runtime] } {
+ return 0
+}
+return 1
[-- Attachment #2: cdivchkld.patch --]
[-- Type: text/x-patch, Size: 758 bytes --]
testsuite: gcc.c-torture/execute/ieee/cdivchkld.c needs fmaxl
The new test gcc.c-torture/execute/ieee/cdivchkld.c needs fmaxl(),
which may not be available, for instance on aarch64-elf with newlib.
As discussed in the PR, requiring c99_runtime enables to skip the test
in this case.
2021-05-04 Christophe Lyon <christophe.lyon@linaro.org>
PR testsuite/100355
gcc/testsuite/
* gcc.c-torture/execute/ieee/cdivchkld.x: New.
diff --git a/gcc/testsuite/gcc.c-torture/execute/ieee/cdivchkld.x b/gcc/testsuite/gcc.c-torture/execute/ieee/cdivchkld.x
new file mode 100644
index 0000000..f798152
--- /dev/null
+++ b/gcc/testsuite/gcc.c-torture/execute/ieee/cdivchkld.x
@@ -0,0 +1,4 @@
+if { [check_effective_target_c99_runtime] } {
+ return 0
+}
+return 1
next reply other threads:[~2021-05-04 20:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 20:57 Christophe Lyon [this message]
2021-05-05 23:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKdteObK-TT06PrFHwHxFDZ39qdzi2tcjnm2R6qboD7PuP9qxg@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--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).