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 2AEE03858285; Wed, 28 Sep 2022 12:58:43 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2AEE03858285
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1664369923;
	bh=K0qhU6zsEV7BzygohPVVeel3RbEHER9Rl+FCBmZ36PM=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=VspRPv30T9Spt6y376GT2JBXdYymlQwB1StE65r3lCDdRtvjp75aReL/Bf4nEqmJ9
	 NDcOMiMjggUPxW2aFug6tMpxSfX2xgUQ9XvwwIrRpWt3raCWWAI21hDasduvlDNRrq
	 8IyF7rNPTSAWtkOkEPYyuL0I4rq53e+Y65apslJM=
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107059] [13 regression] bootstrap failure after
 r13-2887-gb04208895fed34
Date: Wed, 28 Sep 2022 12:58:42 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 13.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus 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: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-107059-4-tBbtwoyyhQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107059-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=3D107059

--- Comment #19 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #18)
> You mean the #c14
comment 14 (< this adds a link)

> change incorrectly adds
>   /tmp/tburnus-gcc-test/gcc/powerpc64le-linux-gnu/include-fixed
> rather than
>   /tmp/tburnus-gcc-test/gcc/include-fixed/powerpc64le-linux-gnu
> to search path?

Maybe. Or rather: Yes, for the *being* *build* compiler (with "xgcc -B
$BUILD/gcc")
it *either* adds the wrong directory
*or* fixinclude creates the wrong directory.

However, for the *installed* compiler, we have:

#include "..." search starts here:
#include <...> search starts here:

/tmp/tburnus-gcc-test-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/inc=
lude
 /usr/local/include
 /tmp/tburnus-gcc-test-inst/include

/tmp/tburnus-gcc-test-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/inc=
lude-fixed/powerpc64le-linux-gnu

/tmp/tburnus-gcc-test-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/inc=
lude-fixed
 /usr/include/powerpc64le-linux-gnu
 /usr/include
End of search list.

And as the fix-include floatn.h is under
/tmp/tburnus-gcc-test-inst/lib/gcc/powerpc64le-unknown-linux-gnu/13.0.0/inc=
lude-fixed/powerpc64le-linux-gnu/bits/floatn.h=