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 E22B8385087B; Fri, 18 Aug 2023 16:27:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E22B8385087B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1692376066;
	bh=n/7rlrIQaK6ecNO67SYkTPEuf/KA+pTrletK+wjzKRE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=XdBeVKDzs9iv2MoQgiGVb6i2PIsKv9qw6/4IqPwfqBVJYZm3CTAAOZ9Pe54P9RQ44
	 a+DJO0ehlaVblZMMK2zuZ56IWrfcYR+2Za3bl8RQWz/QX2PbPfDBDt21YE4WWzuVtm
	 YSD3a9Qn0e2y53mruUhSESC9SDQDZD2+j0g/bPWw=
From: "kito at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/111065] [RISCV] t-linux-multilib specifies incorrect
 multilib reuse patterns
Date: Fri, 18 Aug 2023 16:27:46 +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: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kito at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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-111065-4-YaPV8Dh9ot@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-111065-4@http.gcc.gnu.org/bugzilla/>
References: <bug-111065-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=3D111065

--- Comment #4 from Kito Cheng <kito at gcc dot gnu.org> ---
I guess I skip too much detail here, the multilib for linux isn=E2=80=99t r=
eally honor
to the reause rule in the multilib config file for a while.

That just control how multilib build, e.g. build ilp32 with which arch, and=
 we
will find matched ABI, but why we did that? The reason is simplify the reuse
rule, RISC-V has huge number of extension now, so enumeration the possible
combination are almost impossible.

But why it can=E2=80=99t use same scheme as baremetal? Okay, that=E2=80=99s=
 because we encode
the abi in the path only, unlike baremetal we have encode both abi and arch=
, it
kinda of de facto ABI in linux/glibc, also it not make too much sense to ha=
ving
too much different multilib within a (RISC-V) linux system.=