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 81A70385841D; Wed, 28 Sep 2022 09:46:33 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 81A70385841D
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1664358393;
	bh=rt6bSNaYpBKi24boUeZbHMGY9ATWRDhRfSnyuv1f7yY=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=lIo3/t89mkyFE1PxW94lOLxtWdEvuTdECnUuBDTe0M6AKpqqoPnexh05XofdibKEw
	 7aQlvUzNWlhgO89PTjnFjrjTYOrFJLlJABDSP/l29Td4Ca++ob9kOHSng6HSso+yK6
	 5lfZ4ConctZO0alLYheiO28LwosxtiOTfD4ZXDNc=
From: "jakub 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 09:46:33 +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: jakub 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-MxirjE4qqc@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 #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I wonder how it works for Tobias then.
If the fixincluded headers go to
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/powerpc64le-linux-g=
nu/bits/floatn{,-common}.h
and search path is:
...
 /home/seurer/gcc/git/build/gcc-test/./gcc/include
 /home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed
 /usr/local/include
 /usr/include/powerpc64le-linux-gnu
 /usr/include
then I think it can't find those headers for #include <bits/floatn.h>
Given the above, I think the search paths should be:
...
 /home/seurer/gcc/git/build/gcc-test/./gcc/include
 /home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/powerpc64le-linux-=
gnu
 /home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed
 /usr/local/include
 /usr/include/powerpc64le-linux-gnu
 /usr/include
because the multiarch subdir sits below /usr/include and so is fixincluded
together with it.  I'd be afraid we fixinclude all the other arches if they
are, so if one has
/usr/include/powerpc64le-linux-gnu/bits/floatn.h
/usr/include/x86_64-linux-gnu/bits/floatn.h
both would go to:
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/powerpc64le-linux-g=
nu/bits/floatn.h
/home/seurer/gcc/git/build/gcc-test/./gcc/include-fixed/x86_64-linux-gnu/bi=
ts/floatn.h
so making fixincludes itself multiarch aware is going to be difficult.=