Yes, I would like to do it.
Dongyan Chen
在 2025/6/19 23:17, Kito Cheng 写道:
I guess we should implement an auto generated document for mcpu and
mtune document like what we do for -march.
Dongyan, do you have interest to implement that? :)
On Thu, Jun 19, 2025 at 10:02 PM Jeff Law wrote:
We
On 6/19/25 9:17 AM, Kito Cheng wrote:
I guess we should implement an auto generated document for mcpu and
mtune document like what we do for -march.
Yea, probably. The more of that stuff that's auto generated the better.
It's easily forgotten.
jeff
I guess we should implement an auto generated document for mcpu and
mtune document like what we do for -march.
Dongyan, do you have interest to implement that? :)
On Thu, Jun 19, 2025 at 10:02 PM Jeff Law wrote:
>
>
>
> On 6/19/25 1:55 AM, Kito Cheng wrote:
> > Thanks, pushed with one minor chan
On 6/19/25 1:55 AM, Kito Cheng wrote:
Thanks, pushed with one minor change.
Robin has mentioned that maybe we could name it generic-in-order, but
I think this could be a follow up patch if we want, I would like to
have -mtune=generic even though we added that since clang/LLVM already
provided
Thanks, I found that it can also be solved by changing the default mtune
in file "configure" of riscv-gnu-toolchain and I will prepare a PR to
riscv-gnu-toolchain repo.
Dongyan Chen
在 2025/6/19 15:55, Kito Cheng 写道:
Thanks, pushed with one minor change.
Robin has mentioned that maybe we
Thanks, pushed with one minor change.
Robin has mentioned that maybe we could name it generic-in-order, but
I think this could be a follow up patch if we want, I would like to
have -mtune=generic even though we added that since clang/LLVM already
provided -mtune=generic :)
> diff --git
> a/gcc/t
According to the discussion in
https://gcc.gnu.org/pipermail/gcc-patches/2025-June/686893.html, by creating
a -mtune=generic may be a good idea to slove the question regarding the branch
cost.
Changes for v2:
- Delete the code about -mcpu=generic.
gcc/ChangeLog:
* config/riscv/riscv-cor
