This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] tbb-backend effective target should check ability to link TBB

From: François Dumont <frs dot dumont at gmail dot com>
To: Jonathan Wakely <jwakely at redhat dot com>, Thomas Rodgers <trodgers at redhat dot com>
Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>, gcc-patches <gcc-patches at gcc dot gnu dot org>
Date: Tue, 21 May 2019 22:47:55 +0200
Subject: Re: [PATCH] tbb-backend effective target should check ability to link TBB
References: <xkqeftq5g0ar.fsf@trodgers.remote.f27> <xkqeftp8e7wx.fsf@trodgers.remote.f27> <20190521135056.GN2599@redhat.com>

On 5/21/19 3:50 PM, Jonathan Wakely wrote:

On 20/05/19 21:41 -0700, Thomas Rodgers wrote:

With the addition of "-ltbb" to the v3_target_compile flags (so as to,
you know, actually try to link tbb).

Tested x86_64-linux, committed to trunk.


This didn't work, I still get a FAIL for every pstl test when
tbb.x86_64 and tbb-devel.x86_64 are installed but not tbb.i686.

Adding -v to RUNTESTFLAGS shows -ltbb wasn't being added to the
command, and because the test program didn't actually refer to any TBB
symbols, it still linked successfully.

But the test program still do not refer any TBB symbol. Why is it better? It looks like it could be a preprocess test.

Follow-Ups:
- Re: [PATCH] tbb-backend effective target should check ability to link TBB
  - From: Jonathan Wakely

References:
- Re: [PATCH] tbb-backend effective target should check ability to link TBB
  - From: Thomas Rodgers
- Re: [PATCH] tbb-backend effective target should check ability to link TBB
  - From: Jonathan Wakely

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]