Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Jan 27, 2022)
On 1/26/22 14:04, jia...@iscas.ac.cn wrote: > Hi all, > > There is an agenda for tomorrow's meeting. If you have topics to > discuss or share, please let me know and I can add them to the agenda. > > Agenda: > > > > > > - Bump GCC default ISA spec and got bug report[1] for that. Tried to join the meeting, but it ended early apparently. Using in Debian and Ubuntu binutils 2.38, I see then with GCC 11.2 warnings for every link: /usr/bin/ld: warning: /usr/lib/gcc/riscv64-linux-gnu/10/crtn.o: mis-matched ISA version 2.0 for 'i' extension, the output version is 2.1 /usr/bin/ld: warning: /usr/lib/gcc/riscv64-linux-gnu/10/crtn.o: mis-matched ISA version 2.0 for 'a' extension, the output version is 2.1 /usr/bin/ld: warning: /usr/lib/gcc/riscv64-linux-gnu/10/crtn.o: mis-matched ISA version 2.0 for 'f' extension, the output version is 2.2 /usr/bin/ld: warning: /usr/lib/gcc/riscv64-linux-gnu/10/crtn.o: mis-matched ISA version 2.0 for 'd' extension, the output version is 2.2 Are there any plans to backport the support for ISA 2.1/2.2 to GCC 11? Or do we need to configure binutils to use 2.0 until the compiler is changed to GCC 12? There's also no documentation about that change, at least in binutils. Should that be mentioned in the release notes? Thanks, Matthias
gcc-9-20220127 is now available
Snapshot gcc-9-20220127 is now available on https://gcc.gnu.org/pub/gcc/snapshots/9-20220127/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 9 git branch with the following options: git://gcc.gnu.org/git/gcc.git branch releases/gcc-9 revision 0262ff2333c7ee27d6a96db1fffe153e16cbcd26 You'll find: gcc-9-20220127.tar.xzComplete GCC SHA256=2d762f068cb6ae7aa9f386a6e344906345b7688738592187ae93d107f403e3be SHA1=33affc172191c0d889c4cea92b4c694cd436981a Diffs from 9-20220120 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-9 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Jan 27, 2022)
> -原始邮件- > 发件人: "Matthias Klose" > 发送时间: 2022-01-28 00:18:47 (星期五) > 收件人: jia...@iscas.ac.cn, gcc@gcc.gnu.org, binut...@sourceware.org, g...@sourceware.org, libc-al...@sourceware.org > 抄送: cmuell...@ventanamicro.com, si...@isrc.iscas.ac.cn, philipp.toms...@vrull.eu, nelson@sifive.com, wuwei2...@iscas.ac.cn, kito.ch...@sifive.com, yul...@nj.iscas.ac.cn, shi...@iscas.ac.cn > 主题: Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Jan 27, 2022) > > On 1/26/22 14:04, jia...@iscas.ac.cn wrote: > > Hi all, > > > > There is an agenda for tomorrow's meeting. If you have topics to > > discuss or share, please let me know and I can add them to the agenda. > > > > Agenda: > > > > > > > > > > > > - Bump GCC default ISA spec and got bug report[1] for that. > > Tried to join the meeting, but it ended early apparently. > > Using in Debian and Ubuntu binutils 2.38, I see then with GCC 11.2 warnings for > every link: > > /usr/bin/ld: warning: /usr/lib/gcc/riscv64-linux-gnu/10/crtn.o: mis-matched ISA > version 2.0 for 'i' extension, the output version is 2.1 > /usr/bin/ld: warning: /usr/lib/gcc/riscv64-linux-gnu/10/crtn.o: mis-matched ISA > version 2.0 for 'a' extension, the output version is 2.1 > /usr/bin/ld: warning: /usr/lib/gcc/riscv64-linux-gnu/10/crtn.o: mis-matched ISA > version 2.0 for 'f' extension, the output version is 2.2 > /usr/bin/ld: warning: /usr/lib/gcc/riscv64-linux-gnu/10/crtn.o: mis-matched ISA > version 2.0 for 'd' extension, the output version is 2.2 > > Are there any plans to backport the support for ISA 2.1/2.2 to GCC 11? Or do we > need to configure binutils to use 2.0 until the compiler is changed to GCC 12? > > There's also no documentation about that change, at least in binutils. Should > that be mentioned in the release notes? > > Thanks, Matthias Hi Matthias, Here is a link that Kito Cheng explain this change: https://groups.google.com/a/groups.riscv.org/g/sw-dev/c/aE1ZeHHCYf4 I think you can use aditional option --with-isa-spec=2.2 to solve this problem Good luck, PLCT Jiawei
