From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id 488EA3858D33; Thu, 18 Jan 2024 18:19:29 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 488EA3858D33
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1705601969;
	bh=ju1pbwRJzJOiZI2ZLSGlUSRvOEUXdy5/68/BY2imyNs=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=hKml+DK5JLonFA1rLjp1tJ4JmjJ2qONJdNkJsxzuINHod1+p7QhA3ePGZ48K2V+zW
	 ILxJjfY9FdJ1gULMpwf4XcBiflGwHyiqzOV3S5jeSEF/ZGcUavNP6GEGzmZyCRQBnE
	 tMOyEwdvA/wcHACJlBC2azRUskKcmUaNywA/K+To=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112862] [14 regression] gfortran.dg coarray tests FAIL
 on macOS 12+
Date: Thu, 18 Jan 2024 18:19:28 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 14.0
X-Bugzilla-Keywords: testsuite-fail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: iains at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-112862-4-yj6h2x5OF8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-112862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-112862-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112862

--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to ro@CeBiTec.Uni-Bielefeld.DE from comment #4)
> > --- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
> > OK. So I realise the reason you see this and I wasn't: I have the habit=
 of
> > installing before running the testsuite.  When I test uninstalled, then=
 I get
> > the issue.
>=20
> Right: I always avoid installing before testing to make extra certain to
> test the freshly built bits and nothing else.

I would not have that problem, since I always delete the previous install
(otherwise its shared libraries could be found during the current build, si=
nce
the GCC command lines usually include the installation paths).


> > Now I have a concern that we have instances of -Bpath/to/libsomething/.=
libs
> > that are present to allow for specs substitution and we also need them =
for
> > providing run paths at test time.  BUT, we do not want duplicates (sinc=
e, that
> > triggers a different warning for some Xcode versions, and is inefficien=
t anyway
> > - albeit probably a very minor contribution to testing time).
>=20
> Still there is going to be an impact, even on non-Darwin.  However, this
> duplication of -B and -L options is present all over the testsuite
> already, just nobody cared to do something about it so far.  Those Xcode
> 15 ld warnings my change this, though...

Actually, since -B produces a -L for every -B directory that exists, if we =
add
-B we really ought to omit the -L if it's the same - otherwise we get usele=
ss
duplicates on the link line.  Do you know of any exception to the B implies=
 L?=