https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97409
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96307
Kito Cheng changed:
What|Removed |Added
Priority|P4 |P3
--- Comment #5 from Kito Cheng ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96759
Kito Cheng changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |kito at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96759
Kito Cheng changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98152
Kito Cheng changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98152
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417
--- Comment #55 from Kito Cheng ---
Hi jiawei:
Thanks for the data, the performance changing for coremark-pro seems
interesting, could you find which part generate different code after the patch?
And I am curious what the platform you used for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417
--- Comment #58 from Kito Cheng ---
Hi jiawei:
I would suggest you just using inst count rather than cycle or time for
measuring benchmark if you using qemu, since qemu is functional simulator not
cycle accurate neither nearly-cycle accurate
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417
--- Comment #25 from Kito Cheng ---
Seem like you have add code to gcc/optabs.h and gcc/optabs.c, however those
functions are RISC-V specific, so I would suggest you put in riscv.c and
riscv-protos.h.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417
--- Comment #37 from Kito Cheng ---
Maybe we could add a parameter to indicate the type of memory access,
plain_mem, zext_mem or sext_mem for pass_shorten_memrefs::get_si_mem_base_reg.
e.g.
for (int i = 0; i < 2; i++)
{
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97682
Kito Cheng changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97682
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97417
--- Comment #16 from Kito Cheng ---
> Or maybe we make the choice of zero-extend or sign-extend depend on the mode,
> and use zero-extend for smaller than SImode and sign-extend for SImode and
> larger.
Maybe depend on LOAD_EXTEND_OP?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96307
--- Comment #7 from Kito Cheng ---
Committed fix into trunk, wait one week to commit to gcc 10 branh.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98743
--- Comment #2 from Kito Cheng ---
ICE after g:6fbec038f7a7ddf29f074943611b53210d17c40c, hmmm...interesting...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98743
Kito Cheng changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98596
--- Comment #2 from Kito Cheng ---
Few years ago, Monk and me has write a very detailed cost model for nds32 port,
that way might able to fix the issue and further optimized for the code size
and performance, but...it need lots time to fine tune
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98743
--- Comment #3 from Kito Cheng ---
Seems like g:3e60ddeb8220ed388819bb3f14e8caa9309fd3c2 is the real root cause
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98743
Kito Cheng changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96307
Kito Cheng changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98878
Bug ID: 98878
Summary: Incorrect multilib list for riscv*-rtems
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100647
Bug ID: 100647
Summary: ICE during sms pass
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101275
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98878
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96307
--- Comment #12 from Kito Cheng ---
> This disables the CC_HAS_KASAN_GENERIC config of the kernel, making KASAN
> unavailable.
H, I checked with kernel source code, it only feed
-fsanitize=kernel-address during checking, but in fact it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99314
Kito Cheng changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99702
Kito Cheng changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99702
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99314
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99314
--- Comment #3 from Kito Cheng ---
Thanks for providing environment info, I'll try that soon.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99314
Kito Cheng changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99314
--- Comment #1 from Kito Cheng ---
I didn't see this testcase failed before, and I can't reproduce that on my work
environment, do you mind share your build environment, e.g. the version of gcc
or the distribution version?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98981
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101275
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100316
Kito Cheng changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100316
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102538
Bug ID: 102538
Summary: Wrong narrowing conversion checking for initializer
with union
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102957
--- Comment #3 from Kito Cheng ---
Wait another week for make sure stable and backport to gcc-11 and gcc-10
branch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102957
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
--- Comment #4 from Kito Cheng ---
Hi Andrew:
Thanks for your quick response! the patch is work to me for the testcase,
but...I got seg fault when I built x86 GCC.
Here is a reduced case from gcov, and this testcase also take longer
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
--- Comment #6 from Kito Cheng ---
Reported testcase is OK and I test that patch on riscv64-elf and riscv64-linux
with full gcc testsuite run, both are no regression.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
--- Comment #2 from Kito Cheng ---
Oh, apologize for misleading, it should fixed via pr103231 rather than
pr103254.
it work after g:5deacf6058d1bc7261a75c9fd1f116c4442e9e60, no new file, but it's
not trivial backport-able.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103525
Kito Cheng changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103603
Bug ID: 103603
Summary: [11 Regression] stack overflow on ranger for huge
program, but OK for legacy
Product: gcc
Version: 11.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104219
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853
--- Comment #4 from Kito Cheng ---
Thanks your info, that cause by the default ISA spec version bump issue,
binutils 2.38 and GCC 11.* using different default ISA spec cause this issue,
I've push a patch to GCC 11 branch [1] for this issue,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102957
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853
Kito Cheng changed:
What|Removed |Added
Last reconfirmed||2022-03-30
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853
--- Comment #10 from Kito Cheng ---
I plan to fix that in next few day for trunk and backport to GCC 11.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104219
--- Comment #5 from Kito Cheng ---
I plan back port this fix to GCC 11 branch too, and will close this bug after
back port.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104219
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104219
--- Comment #3 from Kito Cheng ---
Patch posted to mailing list:
https://gcc.gnu.org/pipermail/gcc-patches/2022-January/589225.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104853
--- Comment #13 from Kito Cheng ---
Hi rvalue:
Pushed the fix to trunk and GCC 11 branch for fixing both arch-canonicalize and
multilib-generator script.
Tested GCC 11/trunk with --with-isa-spec=2.2/20191213.
Could you try that to make sure
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109773
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110560
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111037
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111074
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110299
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110277
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111372
--- Comment #5 from Kito Cheng ---
> Ok, but it's better to have configure option or something else just
> for toolchains that definitely do not use vector extension
I can understand that there would be such a demand in the embedded world, but
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109725
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #6
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112431
--- Comment #3 from Kito Cheng ---
Share some thought from my end: we've tried at least 3 different approach on
LLVM side before, and now we model that as "partial early clobber", we plan to
upstream this on LLVM side but just didn't get high
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112433
--- Comment #1 from Kito Cheng ---
Give few more background why LLVM must do that way: LLVM can't allocate new
pseudo register during register allocation process, however spilling vector
register with specific length may require scratch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112092
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111412
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111664
Kito Cheng changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600
--- Comment #14 from Kito Cheng ---
Some info for generated files:
-
File blankcomment code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #13
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111791
Bug ID: 111791
Summary: RISC-V: Strange loop vectorizaion on popcount function
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111926
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111926
--- Comment #2 from Kito Cheng ---
Forgot to mention, personally I love idea to simplify code gen, I could imagine
that's definitely an optimization for specific uarch :)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
--- Comment #4 from Kito Cheng ---
I guess I skip too much detail here, the multilib for linux isn’t really honor
to the reause rule in the multilib config file for a while.
That just control how multilib build, e.g. build ilp32 with which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111065
Kito Cheng changed:
What|Removed |Added
Version|og13 (devel/omp/gcc-13) |14.0
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111037
Bug ID: 111037
Summary: RISC-V: Invalid vsetvli fusion
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112433
--- Comment #4 from Kito Cheng ---
Yeah, 3 major goal in LLVM is improving scheduling, partial spilling and
re-materialization, but none of those points are issue for RISC-V GCC :P
Ref:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105733
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106149
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88345
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #7
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106338
--- Comment #6 from Kito Cheng ---
My understanding is static chain is sort of compiler internal implementation,
any register could be picked if that is not used for passing argument, so I
would also prefer keep that out psABI spec for now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106585
--- Comment #5 from Kito Cheng ---
bset generated after change X to GPR for most zbs pattern:
```
foo:
bseta1,x0,a1
andna0,a0,a1
sext.w a0,a0
ret
```
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106585
Bug ID: 106585
Summary: RISC-V: Mis-optimized code gen for zbs
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106532
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106585
--- Comment #4 from Kito Cheng ---
> It uses X iterator here instead of GPR, hmmm ...
I think that because we have w-variant before, so use X rather than GPR here,
but apparently we should revise this.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108185
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108185
Kito Cheng changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88345
--- Comment #13 from Kito Cheng ---
Patch posted before, but seems like not everybody agree:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603049.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109244
Kito Cheng changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109244
--- Comment #4 from Kito Cheng ---
Gonna commit the fix soon, and following code is the reduced case which is
reduced from your attachment.
Reduced case (reduced by creduce)
typedef int a;
using c = float;
template < typename > using e =
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109228
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109228
Kito Cheng changed:
What|Removed |Added
CC||kito at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108185
Kito Cheng changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108339
Kito Cheng changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109479
Kito Cheng changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109535
--- Comment #5 from Kito Cheng ---
Confirmed the the output is text file, it's just suffixed with .out
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109104
Kito Cheng changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109535
Kito Cheng changed:
What|Removed |Added
Last reconfirmed||2023-04-17
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109535
Kito Cheng changed:
What|Removed |Added
Target Milestone|--- |13.2
Summary|internal compiler
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109547
Kito Cheng changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
1 - 100 of 162 matches
Mail list logo