public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: "Thomas Preud'homme" <thomas.preudhomme@arm.com>,
	       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: Thu, 17 Dec 2015 08:26:00 -0000	[thread overview]
Message-ID: <20151217082549.GR18720@tucnak.redhat.com> (raw)
In-Reply-To: <87fuz1pko0.fsf@kepler.schwinge.homeip.net>

On Thu, Dec 17, 2015 at 09:02:39AM +0100, Thomas Schwinge wrote:
> On Tue, 15 Dec 2015 17:44:59 +0100, I wrote:
> > 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" ]
> > >  }

That change has been obviously bad.  If anything, you want to make it
compile time only, i.e. check_no_compiler_messages_nocache fcilkplus_available assembly
Just look at cilk-plus.exp:
It checks check_effective_target_cilkplus, and performs lots of tests if it
it returns true, and then checks check_libcilkrts_available and performs
further tests.
So, if any use of -fcilkplus fails on your target, then putting it
into check_effective_target_cilkplus is fine, you won't lose any Cilk+
testing that way.  Otherwise, if it is conditional say only some constructs,
say array notation is fine, but _Cilk_for is not, then even that is wrong.

In any case, IMHO the attr-simd-3.c test just should be moved into
c-c++-common/cilk-plus/SE/ directory.

	Jakub

  reply	other threads:[~2015-12-17  8:26 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
2015-12-17  8:03   ` Thomas Schwinge
2015-12-17  8:26     ` Jakub Jelinek [this message]
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=20151217082549.GR18720@tucnak.redhat.com \
    --to=jakub@redhat.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 \
    --cc=thomas@codesourcery.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).