From: Matthias Klose <doko@ubuntu.com>
To: jiawei@iscas.ac.cn, gcc@gcc.gnu.org, binutils@sourceware.org,
gdb@sourceware.org, libc-alpha@sourceware.org
Cc: cmuellner@ventanamicro.com, sinan@isrc.iscas.ac.cn,
philipp.tomsich@vrull.eu, nelson.chu@sifive.com,
wuwei2016@iscas.ac.cn, kito.cheng@sifive.com,
yulong@nj.iscas.ac.cn, shihua@iscas.ac.cn
Subject: Re: [RISCV] RISC-V GNU Toolchain Biweekly Sync-up call (Jan 27, 2022)
Date: Thu, 27 Jan 2022 17:18:47 +0100 [thread overview]
Message-ID: <99921eab-0b07-7792-99de-aa45bc5c86db@ubuntu.com> (raw)
In-Reply-To: <27086da7.1c00e.17e967d235d.Coremail.jiawei@iscas.ac.cn>
On 1/26/22 14:04, jiawei@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
next prev parent reply other threads:[~2022-01-27 16:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 13:04 jiawei
2022-01-26 22:23 ` Philipp Tomsich
2022-01-27 16:18 ` Matthias Klose [this message]
2022-01-28 1:02 ` jiawei
2022-01-28 10:06 ` David Abdurachmanov
2022-01-28 12:29 ` Matthias Klose
2022-02-23 13:01 jiawei
2022-03-09 12:16 jiawei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99921eab-0b07-7792-99de-aa45bc5c86db@ubuntu.com \
--to=doko@ubuntu.com \
--cc=binutils@sourceware.org \
--cc=cmuellner@ventanamicro.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=jiawei@iscas.ac.cn \
--cc=kito.cheng@sifive.com \
--cc=libc-alpha@sourceware.org \
--cc=nelson.chu@sifive.com \
--cc=philipp.tomsich@vrull.eu \
--cc=shihua@iscas.ac.cn \
--cc=sinan@isrc.iscas.ac.cn \
--cc=wuwei2016@iscas.ac.cn \
--cc=yulong@nj.iscas.ac.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).