https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118487
Christoph Müllner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118487
--- Comment #3 from Christoph Müllner ---
My initial comment about the need to sanitize the mask elements of
VEC_PERM_EXPR was correct, but there is nothing to be done for that, because
this is handled by ccp1.
The ICE reported here comes from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118487
Christoph Müllner changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from Christ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 117079, which changed state.
Bug 117079 Summary: [15 Regression] FAIL: gcc.target/i386/pr105493.c since
r15-2820-gab18785840d7b8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117079
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117079
Christoph Müllner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117079
--- Comment #4 from Christoph Müllner ---
The reason that we don't have "MEM " in the dump
anymore is that we now have "MEM ".
Further, the size of the function in the test case shrinks from 225
instructions down to 109 (almost all vector instr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118149
Christoph Müllner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118149
Christoph Müllner changed:
What|Removed |Added
Last reconfirmed||2024-12-20
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116347
Christoph Müllner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 117830, which changed state.
Bug 117830 Summary: [15 Regression] Miscompilation of 464.h264ref at -O2
-march=generic since r15-5563-g1c4d39ada33d36
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117830
What|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117830
Christoph Müllner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117830
--- Comment #6 from Christoph Müllner ---
Patch on list:
https://gcc.gnu.org/pipermail/gcc-patches/2024-December/672065.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116347
Christoph Müllner changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |cmuellner at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117830
--- Comment #5 from Christoph Müllner ---
Thank you for reporting this!
I can reproduce this issue on x86_64 (I did not test on other architectures).
I have also confirmed that the suspected change (1c4d39ada33d) causes this
by validating that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117728
Christoph Müllner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117728
Christoph Müllner changed:
What|Removed |Added
Last reconfirmed||2024-11-21
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116347
Christoph Müllner changed:
What|Removed |Added
Last reconfirmed|2024-10-17 00:00:00 |2024-10-22
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111565
Christoph Müllner changed:
What|Removed |Added
CC||cmuellner at gcc dot gnu.org
Ev
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116720
Christoph Müllner changed:
What|Removed |Added
Last reconfirmed||2024-10-17
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116347
Christoph Müllner changed:
What|Removed |Added
Last reconfirmed||2024-10-17
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116593
Christoph Müllner changed:
What|Removed |Added
Target|Riscv |riscv
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116591
Christoph Müllner changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Keywords|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116590
Christoph Müllner changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114326
Christoph Müllner changed:
What|Removed |Added
CC||cmuellner at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109393
Christoph Müllner changed:
What|Removed |Added
CC||cmuellner at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116349
--- Comment #7 from Christoph Müllner ---
(In reply to seurer from comment #6)
> I am seeing this same failure in doing a bootstrap build during stage 2 on
> powerpc64:
A fix that is confirmed to work on AArch64 and x86-64 has been posted here
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116353
--- Comment #7 from Christoph Müllner ---
> To add on to the info provided by Manolis, this is the diff for the proposed
> fix:
>
> diff --git a/gcc/ifcvt.cc b/gcc/ifcvt.cc
> index 3e25f30b67e..da59c907891 100644
> --- a/gcc/ifcvt.cc
> +++ b/gc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116131
--- Comment #5 from Christoph Müllner ---
I've prepared a patchset that eliminates the optimization patterns for
XThead(F)MemIdx, which produce the non-canonical MEMs. As a side-effect, this
change also fixes the issue reported here. However, it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116033
Christoph Müllner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116131
--- Comment #3 from Christoph Müllner ---
After passing the tests, I've posted the patch on the mailing list:
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/658726.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116131
Christoph Müllner changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116131
--- Comment #2 from Christoph Müllner ---
Thank you for reporting!
A first analysis showed, that adding more extensions does not change anything.
E.g. rv32gc_xtheadmemidx also triggers the error. However, rv64i_xtheadmemidx
is not affected. Als
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116035
Christoph Müllner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116033
--- Comment #2 from Christoph Müllner ---
Jeff Law claimed that th_classify_address() is likely missing a mode check.
I checked that before, and there is a mode check there.
But, after this comment, I challenged the test and indeed:
if (!(INTE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116033
Christoph Müllner changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116035
--- Comment #4 from Christoph Müllner ---
I understood this as GCC 14 and 15 (i.e., master) show this issue.
Testing with GCC 13 shows:
error: '-march=rv64g_xtheadmemidx_zba': unexpected ISA string at end: 'zba'
The issue does not apply to GC
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116035
--- Comment #2 from Christoph Müllner ---
Proposed fix has been posted on the mailing list:
https://gcc.gnu.org/pipermail/gcc-patches/2024-July/658091.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116035
Christoph Müllner changed:
What|Removed |Added
Last reconfirmed||2024-07-23
Status|UNCON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115562
Christoph Müllner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115554
Christoph Müllner changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115562
--- Comment #1 from Christoph Müllner ---
This issue was discovered while analyzing a build issue with a patchset
to introduce optimized string processing routines for RISC-V in glibc.
See also:
https://sourceware.org/pipermail/libc-alpha/202
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115562
Bug ID: 115562
Summary: RISC-V: ICE because of reused fndecl with target-arch
attribute
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115554
--- Comment #1 from Christoph Müllner ---
Forgot to mention:
The ICE is triggered by an assertion in riscv_func_target_put(), which ensures
we don't have more than one target-arch attribute in one function declaration.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115554
Bug ID: 115554
Summary: RISC-V: ICE in case of multiple target-arch attributes
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Comp
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115344
Bug ID: 115344
Summary: Missing loop counter reversal
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111501
Christoph Müllner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111501
Christoph Müllner changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassig
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11
Christoph Müllner changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114673
Bug ID: 114673
Summary: RISC-V: "L" constraint cannot be used for lui in
inline asm
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114194
Christoph Müllner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114194
Christoph Müllner changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |cmuellner at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114160
Christoph Müllner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114160
Christoph Müllner changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |cmuellner at gcc dot
gnu.org
53 matches
Mail list logo
