Hi Tobias,
> I have also an alternative version:
>
> * For in-build-dir test runs, do as with previous patch, i.e. add
> "-lquadmath" to the "xgcc" call if the directory is available.
>
> * For installed-compiler test runs, the new patch uses GFORTRAN_UNDER_TEST
> / GXX_UNDER_TEST
> (It would
Thanks for the review. I have now committed this version as r276754
(with splitting the long line).
If someone prefers the other variant or bits of it, I will do it as
follow up.
Cheers,
Tobias
On 10/9/19 9:43 AM, Jakub Jelinek wrote:
On Tue, Oct 08, 2019 at 08:33:03PM +0200, Tobias
I have also an alternative version:
* For in-build-dir test runs, do as with previous patch, i.e. add
"-lquadmath" to the "xgcc" call if the directory is available.
* For installed-compiler test runs, the new patch uses
GFORTRAN_UNDER_TEST / GXX_UNDER_TEST
(It would also use them with
On Tue, Oct 08, 2019 at 08:33:03PM +0200, Tobias Burnus wrote:
> libgomp/
> * testsuite/libgomp.fortran/fortran.exp: Add -lquadmath if available.
> * testsuite/libgomp.oacc-fortran/fortran.exp: Ditto.
>
> diff --git a/libgomp/testsuite/libgomp.fortran/fortran.exp
>
The test cases in GCC's libraries run via DejaGNU's "[find_gcc]" –
unless the compiler has been explicitly provided. [1] That means that by
default everything runs with "/gcc/xgcc" – at least for an
in-build-dir test run.
As that's the C driver, specific libraries such as "-lgfortran" or
