This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
RE: Testsuite / Cilk Plus: Include library path in compile flags in gcc.dg/cilk-plus/cilk-plus.exp
- From: "Iyer, Balaji V" <balaji dot v dot iyer at intel dot com>
- To: Joseph Myers <joseph at codesourcery dot com>, Jeff Law <law at redhat dot com>
- Cc: Tobias Burnus <burnus at net-b dot de>, gcc patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 30 Oct 2013 17:16:56 +0000
- Subject: RE: Testsuite / Cilk Plus: Include library path in compile flags in gcc.dg/cilk-plus/cilk-plus.exp
- Authentication-results: sourceware.org; auth=none
- References: <5270E0CD dot 9040600 at net-b dot de> <BF230D13CA30DD48930C31D4099330003A49500B at FMSMSX101 dot amr dot corp dot intel dot com> <52713CF8 dot 8030808 at redhat dot com> <Pine dot LNX dot 4 dot 64 dot 1310301714430 dot 22878 at digraph dot polyomino dot org dot uk>
> -----Original Message-----
> From: Joseph Myers [mailto:joseph@codesourcery.com]
> Sent: Wednesday, October 30, 2013 1:15 PM
> To: Jeff Law
> Cc: Iyer, Balaji V; Tobias Burnus; gcc patches
> Subject: Re: Testsuite / Cilk Plus: Include library path in compile flags in
> gcc.dg/cilk-plus/cilk-plus.exp
>
> On Wed, 30 Oct 2013, Jeff Law wrote:
>
> > /* { dg-do compile } */
> > /* { dg-do run { target i?86-*-* x86-64-*-* } } */
>
> But with an effective-target keyword cilkplusrts or similar, rather than
> hardcoding the same list of targets in lots of places, please.
>
Wow, I didn't know you could do that. Do you have an example where it is done that I can model after?
> --
> Joseph S. Myers
> joseph@codesourcery.com