From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 611C73858D37; Thu, 25 May 2023 22:04:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 611C73858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1685052285; bh=9KSI1hOscQplSSNVLczV1OJUIvFV8uautCtCa3nPTdw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=y2UhRmP0AEeojiJSUsxECYSSbMbmjaWsKT+mqHzQiwiOYuFBBd1pXhbzvGD3YVNUd U0aV5Oh7S9n0Omyox9B+PekPs8+c+b4WrfRgJaYyViHWybrWy2m3YvGFU6Ms2M+SrF HAtUr/IA7k9y6+EKrtgw6Lbq+VfeK6CCOG07XNGs= From: "tschwinge at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/109951] [14 Regression] libgomp, testsuite: non-native multilib c++ tests fail on Darwin. Date: Thu, 25 May 2023 22:04:44 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: testsuite X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: testsuite-fail X-Bugzilla-Severity: normal X-Bugzilla-Who: tschwinge at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 14.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc bug_status cf_reconfirmed_on everconfirmed Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D109951 Thomas Schwinge changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |macro at orcam dot me.uk Status|UNCONFIRMED |NEW Last reconfirmed| |2023-05-25 Ever confirmed|0 |1 --- Comment #3 from Thomas Schwinge --- Iain, sorry for this; let's track this down. Looking at your "test x86_64 multilib on i686" case. First, is my understanding correct, that 'GXX_UNDER_TEST' 'i686-apple-darwin9/libgomp/testsuite/site.exp' does contain the correct flags/paths for the default ("native", "i686") multilib, but incorrect for = the other ("non-native", "x86_64") multilib? Conversely, would 'i686-apple-darwin9/x86_64/libgomp/testsuite/site.exp' contain the correct flags/paths for the other ("non-native", "x86_64") multilib? (..., but that latter file is never used, always the former 'site.exp'; similar to my "Ind= eed there is some confusion there" comment in -- = but that one's benign, in contrast to your case). Second, do you not have similar confusion in 'GCC_UNDER_TEST' and 'GFORTRAN_UNDER_TEST' flags/paths? (May help me to attach all the relevant 'site.exp' files.) Third, see Maciej's Subversion r279708 (Git commit c8e759b4215ba4b376c9d468aeffe163b3d520f0) "libgomp/test: Fix compilation for build sysroot", followed by Git commit 749bd22ddc50b5112e5ed506ffef7249bf8e= 6fb3 "libgomp/test: Remove a build sysroot fix regression" (for libgomp, and similarly other commits for a number of (but not all?) other GCC target libraries). This is what started capturing 'CC' for test-time use as 'GCC_UNDER_TEST', and this is what in recent commit 11f4d483600b5788a3d1cf1527e838e4a7ed1455 "libgomp testsuite: As appropriate, use the 'gcc', 'g++', 'gfortran' driver [PR91884]" I've then extended for 'CXX': 'GXX_UNDER_TEST', 'FC': 'GFORTRAN_UNDER_TEST'. I however don't understand yet the original intent of his change; in my understanding, and = as has been the case before, we'd just get 'GCC_UNDER_TEST' etc. populated by 'find_gcc' etc.=