Bug#926751: gcc-riscv64-linux-gnu: Doesn't work with all valid abi combinations.
Package: gcc-riscv64-linux-gnu
Version: 4:8.3.0-2
Severity: normal
Dear Maintainer,
My RISC V64 implementation doesn't have floating point, so I'm trying
to compile with
-march=rv64imac -mabi=lp64
I see:
$ riscv64-linux-gnu-gcc -mabi=lp64 -march=rv64imac x.c
In file included from /usr/riscv64-linux-gnu/include/features.h:448,
from /usr/riscv64-linux-gnu/include/bits/libc-header-start.h:3,
from /usr/riscv64-linux-gnu/include/stdio.h:27,
from x.c:1:
/usr/riscv64-linux-gnu/include/gnu/stubs.h:8:11: fatal error: gnu/stubs-lp64.h: No such file or directory
# include <gnu/stubs-lp64.h>
compilation terminated.
for a simple hello world program.
It looks as if only march=rv64imafdc/mabi=lp64d is supported; please
can the other valid combinations be supported as well?
The current list is:
march=rv32i/mabi=ilp32
march=rv32im/mabi=ilp32
march=rv32iac/mabi=ilp32
march=rv32imac/mabi=ilp32
march=rv32imafc/mabi=ilp32f
march=rv64imac/mabi=lp64
march=rv64imafdc/mabi=lp64d
Peter C
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf, armel, i386, powerpc, arm64, riscv64
Kernel: Linux 5.0.0-rc4-00001-g4aa9fc2a435a (SMP w/8 CPU cores)
Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gcc-riscv64-linux-gnu depends on:
ii cpp-riscv64-linux-gnu 4:8.3.0-2
ii gcc-8-riscv64-linux-gnu 8.3.0-4cross2
Versions of packages gcc-riscv64-linux-gnu recommends:
ii libc6-dev-riscv64-cross [libc-dev-riscv64-cross] 2.28-7cross1
Versions of packages gcc-riscv64-linux-gnu suggests:
ii autoconf 2.69-11
ii automake 1:1.16.1-4
ii bison 2:3.3.2.dfsg-1
ii flex 2.6.4-6.2
ii gcc-doc 5:7.2.0-2
pn gdb-riscv64-linux-gnu <none>
ii libtool 2.4.6-10
ii make 4.2.1-1.2
ii manpages-dev 4.16-1
-- no debconf information
Reply to: