Hi Chung-Lin,
> sorry for the late reply.
No worries.
> The 'AM_RUNTESTFLAGS = --tool_exec "$(CC)"' does work for us, but only
> because you backed out the change
> from libgomp-test-support.exp, and our installed testing doesn't use the
> libgomp/testsuite/Makefile.* files
> (we invoke
Hi Maciej,
sorry for the late reply.
On 2020/2/1 5:46 AM, Maciej W. Rozycki wrote:
On Tue, 21 Jan 2020, Maciej W. Rozycki wrote:
I'll give your proposal a shot and I'm lucky enough to have a build
configuration where I can have no compiler preinstalled, so at least I can
check if testing
On Tue, 21 Jan 2020, Maciej W. Rozycki wrote:
> I'll give your proposal a shot and I'm lucky enough to have a build
> configuration where I can have no compiler preinstalled, so at least I can
> check if testing with your change applied correctly picks the newly built
> uninstalled compiler
On Tue, 14 Jan 2020, Chung-Lin Tang wrote:
> Can you test if the attached patch works for you? The patch exports the build
> sysroot
> setting from the toplevel to target library subdirs, and adds the --sysroot=
> option
> when doing build-tree testing (I assume that blddir != "" test is
On 2020/1/6 11:25 PM, Maciej W. Rozycki wrote:
Overall if libgomp-test-support.exp is considered appropriate for
standalone testing, then I think two solutions are possible here:
1. An option is added to libgomp's $CC such that the compiler is able to
make builds involving the offload
Hi Maciej,
On 1/6/20 4:25 PM, Maciej W. Rozycki wrote:
Without the patch, the compiler is found (with [find_gcc] I suppose) and
invoked as x86_64-none-linux-gnu-gcc. That works fine for us, but we do
(I think) "installed testing", which IIUC is atypical.
[…]
However before I make any definite
Hi Julian,
> FYI: This patch seems to be causing problems for our (internal -- as
> you know!) test harness. I'm not sure if it's a local issue (or at least
> something we can work around here), or a problem with the patch itself
> though.
I'm sorry to break your setup. I'm currently a little
Hi Maciej,
On Sun, 22 Dec 2019 00:43:54 + (GMT)
"Maciej W. Rozycki" wrote:
> On Fri, 20 Dec 2019, Mike Stump wrote:
>
> > >> This patch series addresses a problem with the testsuite
> > >> compiler being set up across libatomic, libffi, libgo, libgomp
> > >> with no correlation whatsoever
On Fri, 20 Dec 2019, Mike Stump wrote:
> >> This patch series addresses a problem with the testsuite compiler being
> >> set up across libatomic, libffi, libgo, libgomp with no correlation
> >> whatsoever to the target compiler being used in GCC compilation.
> >> Consequently there in no
On Dec 16, 2019, at 4:06 PM, Maciej W. Rozycki wrote:
>
> On Mon, 11 Nov 2019, Maciej W. Rozycki wrote:
>
>> This patch series addresses a problem with the testsuite compiler being
>> set up across libatomic, libffi, libgo, libgomp with no correlation
>> whatsoever to the target compiler
On Mon, 11 Nov 2019, Maciej W. Rozycki wrote:
> This patch series addresses a problem with the testsuite compiler being
> set up across libatomic, libffi, libgo, libgomp with no correlation
> whatsoever to the target compiler being used in GCC compilation.
> Consequently there in no
11 matches
Mail list logo
