From: Thomas Schwinge <thomas@codesourcery.com>
To: Thomas Preud'homme <thomas.preudhomme@arm.com>
Cc: Jeff Law <law@redhat.com>, <gcc-patches@gcc.gnu.org>,
Tobias Burnus <burnus@net-b.de>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Subject: Re: [PATCH, testsuite] Fix PR68629: attr-simd-3.c failure on arm-none-eabi targets
Date: Tue, 15 Dec 2015 16:45:00 -0000 [thread overview]
Message-ID: <877fkfhd9w.fsf@kepler.schwinge.homeip.net> (raw)
In-Reply-To: <000301d13267$d8d086e0$8a7194a0$@arm.com>
[-- Attachment #1: Type: text/plain, Size: 2407 bytes --]
Hi!
On Wed, 9 Dec 2015 17:56:13 +0800, "Thomas Preud'homme" <thomas.preudhomme@arm.com> wrote:
> c-c++-common/attr-simd-3.c fails to compile on arm-none-eabi targets due to -fcilkplus needing -pthread which is not available for those targets. This patch solves this issue by adding a condition to the cilkplus effective target that compiling with -fcilkplus succeeds and requires cilkplus as an effective target for attr-simd-3.c testcase.
> PR testsuite/68629
> * lib/target-supports.exp (check_effective_target_cilkplus): Also
> check that compiling with -fcilkplus does not give an error.
> * c-c++-common/attr-simd-3.c: Require cilkplus effective target.
> --- a/gcc/testsuite/lib/target-supports.exp
> +++ b/gcc/testsuite/lib/target-supports.exp
> @@ -1432,7 +1432,12 @@ proc check_effective_target_cilkplus { } {
> if { [istarget avr-*-*] } {
> return 0;
> }
> - return 1
> + return [ check_no_compiler_messages_nocache fcilkplus_available executable {
> + #ifdef __cplusplus
> + extern "C"
> + #endif
> + int dummy;
> + } "-fcilkplus" ]
> }
>
> proc check_linker_plugin_available { } {
>
>
> Testsuite shows no regression when run with
> + an arm-none-eabi GCC cross-compiler targeting Cortex-M3
> + a bootstrapped x86_64-linux-gnu GCC native compiler
With this committed in r231605, I now see all gcc/testsuite/ Cilk+
testing disappear for "configure && make && make check", because of:
Executing on host: [...]/build-gcc/gcc/xgcc -B[...]/build-gcc/gcc/ fcilkplus_available14337.c -fno-diagnostics-show-caret -fdiagnostics-color=never -fcilkplus -lm -o fcilkplus_available14337.exe (timeout = 300)
spawn [...]/build-gcc/gcc/xgcc -B[...]/build-gcc/gcc/ fcilkplus_available14337.c -fno-diagnostics-show-caret -fdiagnostics-color=never -fcilkplus -lm -o fcilkplus_available14337.exe
xgcc: error: libcilkrts.spec: No such file or directory
compiler exited with status 1
Can you confirm that in your build/test tree, the compiler is picking up
the build-tree libcilkrts, and not the one from /usr/lib/ (or similar)?
Long ago, in r208889, a similar problem has been diagnosed and fixed by
Rainer and Tobias (CCed just in case),
<http://news.gmane.org/find-root.php?message_id=%3C53336904.5010003%40net-b.de%3E>,
so I wonder what broke now?
Grüße
Thomas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-12-15 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 9:56 Thomas Preud'homme
2015-12-10 21:50 ` Jeff Law
2015-12-15 16:45 ` Thomas Schwinge [this message]
2015-12-17 8:03 ` Thomas Schwinge
2015-12-17 8:26 ` Jakub Jelinek
2015-12-17 8:34 ` Thomas Preud'homme
2015-12-17 8:44 ` Thomas Preud'homme
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=877fkfhd9w.fsf@kepler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=burnus@net-b.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=thomas.preudhomme@arm.com \
/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).