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 240C43858D37; Thu, 29 Jun 2023 08:02:53 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 240C43858D37
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1688025773;
	bh=BmyBPIA+y8y9BgaBas2lgyOpg0ZZvKE+diMF8I6zfr8=;
	h=From:To:Subject:Date:From;
	b=NGdNQcItFPdzv6oXGB73CWDA5MozqoAzBfKE+x9VWs7gt70iXQmHMAldK/MRCitHx
	 JO81ogBpwoEt544KJSax258wB6rrCCWW16e2Kn1tSJKtD3QHXKEDOKTKJTaiRSqDdB
	 Rg9PASAL8arnpHOmG970cjN+gp5Wiob+mRn5o0Gc=
From: "bmeng.cn at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/110478] New: RISC-V multilib gcc zicsr in the -march
 causing incorrect libgcc to be used
Date: Thu, 29 Jun 2023 08:02:49 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 13.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bmeng.cn at gmail dot com
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: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-110478-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=3D110478

            Bug ID: 110478
           Summary: RISC-V multilib gcc zicsr in the -march causing
                    incorrect libgcc to be used
           Product: gcc
           Version: 13.1.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: driver
          Assignee: unassigned at gcc dot gnu.org
          Reporter: bmeng.cn at gmail dot com
  Target Milestone: ---

Using the prebuilt toolchain from kernel.org to test this.

$ cd /tmp
$ wget
https://mirrors.edge.kernel.org/pub/tools/crosstool/files/bin/x86_64/13.1.0=
/x86_64-gcc-13.1.0-nolibc-riscv64-linux.tar.xz
$ tar xf x86_64-gcc-13.1.0-nolibc-riscv64-linux.tar.xz
$ cd /tmp/gcc-13.1.0-nolibc/riscv64-linux/bin
$ ./riscv64-linux-gcc -march=3Drv64gc -mabi=3Dlp64 -print-libgcc-file-name
/tmp/gcc-13.1.0-nolibc/riscv64-linux/bin/../lib/gcc/riscv64-linux/13.1.0/li=
b64/lp64/libgcc.a
$ ./riscv64-linux-gcc -march=3Drv32gc -mabi=3Dilp32 -print-libgcc-file-name
/tmp/gcc-13.1.0-nolibc/riscv64-linux/bin/../lib/gcc/riscv64-linux/13.1.0/li=
b32/ilp32/libgcc.a

$ ./riscv64-linux-gcc -march=3Drv64gc_zicsr -mabi=3Dlp64 -print-libgcc-file=
-name
/tmp/gcc-13.1.0-nolibc/riscv64-linux/bin/../lib/gcc/riscv64-linux/13.1.0/li=
bgcc.a
$ ./riscv64-linux-gcc -march=3Drv32gc_zicsr -mabi=3Dilp32 -print-libgcc-fil=
e-name
/tmp/gcc-13.1.0-nolibc/riscv64-linux/bin/../lib/gcc/riscv64-linux/13.1.0/li=
bgcc.a

As you can see from above, without "zicsr" in the "-march", the libgcc path
correctly reflects its multilib configuration, i.e.: 64-bit will link the
libgcc.a in the lib64 sub-directory.

But with "zicsr" in the "-march", the libgcc path is always the non-multilib
version.

The toolchain was configured by:

$ ./riscv64-linux-gcc -###
Using built-in specs.
COLLECT_GCC=3D./riscv64-linux-gcc
COLLECT_LTO_WRAPPER=3D/tmp/gcc-13.1.0-nolibc/riscv64-linux/bin/../libexec/g=
cc/riscv64-linux/13.1.0/lto-wrapper
Target: riscv64-linux
Configured with: /home/arnd/git/gcc/configure --host=3Dx86_64-linux-gnu
--build=3Daarch64-linux --target=3Driscv64-linux --enable-targets=3Dall
--prefix=3D/home/arnd/cross/x86_64/gcc-13.1.0-nolibc/riscv64-linux
--enable-languages=3Dc --without-headers --disable-bootstrap --disable-nls
--disable-threads --disable-shared --disable-libmudflap --disable-libssp
--disable-libgomp --disable-decimal-float --disable-libquadmath
--disable-libatomic --disable-libcc1 --disable-libmpx --enable-checking=3Dr=
elease
--with-static-standard-libraries
Thread model: single
Supported LTO compression algorithms: zlib zstd
gcc version 13.1.0 (GCC)=20


It seems this multilib bug was introduced when zicsr was introduced to RISC=
-V
GCC.=