From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Saleem Abdulrasool <abdulras@google.com>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: avoid enabling vectorized code generation
Date: Fri, 16 Dec 2022 19:45:21 +0000 [thread overview]
Message-ID: <39636675da60fc6c54cc8bbab64ddbac@codethink.co.uk> (raw)
In-Reply-To: <20221216185012.2342675-1-abdulras@google.com>
On 2022-12-16 18:50, Saleem Abdulrasool wrote:
> The compiler is free to generate vectorized operations for zero'ing
> memory. The kernel does not use the vector unit on RISCV, similar to
> architectures such as x86 where we use `-mno-mmx` et al to prevent the
> implicit vectorization. Perform a similar check for
> `-mno-implicit-float` to avoid this on RISC-V targets.
I'm not sure if we should be emitting either of the vector or floating
point instrucitons in the kernel without explicitly marking the section
of code which is using them such as specific accelerator blocks.
--
Ben
next prev parent reply other threads:[~2022-12-16 19:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 18:50 [PATCH] riscv: avoid enabling vectorized code generation Saleem Abdulrasool
2022-12-16 19:05 ` Conor Dooley
2022-12-16 19:45 ` Ben Dooks [this message]
2022-12-16 19:54 ` Palmer Dabbelt
2022-12-16 20:56 ` Saleem Abdulrasool
2022-12-17 2:02 ` Conor Dooley
2022-12-19 15:21 ` Saleem Abdulrasool
2022-12-19 16:51 ` Conor Dooley
2022-12-21 16:17 ` Bin Meng
2022-12-21 17:39 ` Saleem Abdulrasool
2022-12-22 9:40 ` Bin Meng
2022-12-22 15:23 ` Saleem Abdulrasool
2022-12-23 6:57 ` Bin Meng
2022-12-27 15:24 ` Saleem Abdulrasool
2023-02-08 17:56 ` Palmer Dabbelt
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=39636675da60fc6c54cc8bbab64ddbac@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=abdulras@google.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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