From: Tom Rini <trini@konsulko.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Rick Chen <rick@andestech.com>, Leo <ycliang@andestech.com>,
Simon Glass <sjg@chromium.org>,
Alexandre Ghiti <alexandre.ghiti@canonical.com>,
Aurelien Jarno <aurelien@aurel32.net>,
u-boot@lists.denx.de, Bin Meng <bmeng.cn@gmail.com>,
Heiko Stuebner <heiko@sntech.de>,
Christian Stewart <christian@paral.in>
Subject: Re: [PATCH v4 3/3] riscv: Fix build against binutils 2.38
Date: Fri, 7 Oct 2022 11:50:02 -0400 [thread overview]
Message-ID: <20221007155002.GP3044094@bill-the-cat> (raw)
In-Reply-To: <20221003160754.6991-4-heinrich.schuchardt@canonical.com>
[-- Attachment #1: Type: text/plain, Size: 1317 bytes --]
On Mon, Oct 03, 2022 at 06:07:54PM +0200, Heinrich Schuchardt wrote:
> From: Alexandre Ghiti <alexandre.ghiti@canonical.com>
>
> The following description is copied from the equivalent patch for the
> Linux Kernel proposed by Aurelien Jarno:
>
> >From version 2.38, binutils default to ISA spec version 20191213. This
> means that the csr read/write (csrr*/csrw*) instructions and fence.i
> instruction has separated from the `I` extension, become two standalone
> extensions: Zicsr and Zifencei. As the kernel uses those instruction,
> this causes the following build failure:
>
> arch/riscv/cpu/mtrap.S: Assembler messages:
> arch/riscv/cpu/mtrap.S:65: Error: unrecognized opcode `csrr a0,scause'
> arch/riscv/cpu/mtrap.S:66: Error: unrecognized opcode `csrr a1,sepc'
> arch/riscv/cpu/mtrap.S:67: Error: unrecognized opcode `csrr a2,stval'
> arch/riscv/cpu/mtrap.S:70: Error: unrecognized opcode `csrw sepc,a0'
>
> Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
> Tested-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> Tested-by: Heiko Stuebner <heiko@sntech.de>
> Tested-by: Christian Stewart <christian@paral.in>
> Reviewed-by: Rick Chen <rick@andestech.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-10-07 15:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 16:07 [PATCH v4 0/3] riscv: Fix build against binutils 2.38 Heinrich Schuchardt
2022-10-03 16:07 ` [PATCH v4 1/3] docker: install riscv32 toolchain Heinrich Schuchardt
2022-10-03 17:03 ` Tom Rini
[not found] ` <HK0PR03MB29949BBAFB1A6A2CAE54A7F0C15A9@HK0PR03MB2994.apcprd03.prod.outlook.com>
2022-10-05 2:15 ` Rick Chen
2022-10-07 15:49 ` Tom Rini
2022-10-03 16:07 ` [PATCH v4 2/3] buildman: differentiate between riscv32, riscv64 Heinrich Schuchardt
2022-10-03 16:44 ` Simon Glass
2022-10-05 6:53 ` Heinrich Schuchardt
[not found] ` <HK0PR03MB29947226B5A91B54EBB9FF28C15A9@HK0PR03MB2994.apcprd03.prod.outlook.com>
2022-10-05 2:18 ` Rick Chen
2022-10-07 15:49 ` Tom Rini
2022-10-03 16:07 ` [PATCH v4 3/3] riscv: Fix build against binutils 2.38 Heinrich Schuchardt
2022-10-07 15:50 ` Tom Rini [this message]
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=20221007155002.GP3044094@bill-the-cat \
--to=trini@konsulko.com \
--cc=alexandre.ghiti@canonical.com \
--cc=aurelien@aurel32.net \
--cc=bmeng.cn@gmail.com \
--cc=christian@paral.in \
--cc=heiko@sntech.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=rick@andestech.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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