https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113742
--- Comment #1 from Kito Cheng ---
Thanks, forward and assigned this to our (SiFive) engineer :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115725
--- Comment #2 from Kito Cheng ---
TU may not help for this case since we can't guarantee it's use v1 outside, I
mean the argument is passed via a1 (pointer) rather than passed via v1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115725
--- Comment #12 from Kito Cheng ---
Qemu has provide two option to fill up all-one to agnostic policy:
rvv_ta_all_1s and rvv_ma_all_1s*, I guess we could enable that by default in
riscv-gnu-toolchain to discover more potential bugs.
* qemu-r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115725
--- Comment #13 from Kito Cheng ---
FYI: PR for riscv-gnu-toolchain:
https://github.com/riscv-collab/riscv-gnu-toolchain/pull/1501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115795
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115995
--- Comment #3 from Kito Cheng ---
We have an internal qemu patch for adding an option to trigger this damm
behavior by default, and plan to upstream soon...let me ask our Qemu folk if I
can get the patch out first.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116111
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #2
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: kito at gcc dot gnu.org
CC: jeffreyalaw at gmail dot com, juzhe.zhong at rivai dot ai,
palmer at gcc dot gnu.org, pan2.li at intel dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117955
--- Comment #4 from Kito Cheng ---
I can't reproduce that by the top of trunk with your option, could you check
does the bug still can be reproduced by trunk?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118827
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #3
: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: kito at gcc dot gnu.org
Target Milestone: ---
Created attachment 59955
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59955&action=edit
Reduced testcase f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118182
--- Comment #2 from Kito Cheng ---
(on the train yet but I can describe few details for my current solution
1. Always use vl=1 for vfmv.s.f
- this will introduce one extra vsetvli, but at least it correct, and LLVM use
same code gen as well
2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118384
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118182
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119477
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116125
--- Comment #10 from Kito Cheng ---
ping, does it possible to back port to release branches? it seems land on trunk
for a while :)
-optimization
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: kito at gcc dot gnu.org
Target Milestone: ---
Target: riscv
How to reproduce:
```shell
$ riscv64-unknown-linux-gnu-gcc test.cc -S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119832
--- Comment #1 from Kito Cheng ---
Created attachment 61135
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61135&action=edit
0001-RISC-V-Implement-TARGET_MODE_CONFLUENCE.patch
My working patch for this bug
201 - 218 of 218 matches
Mail list logo