https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|13.3|13.4
--- Comment #8 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Richard Biener changed:
What|Removed |Added
Target Milestone|13.2|13.3
--- Comment #7 from Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Richard Biener changed:
What|Removed |Added
Target Milestone|13.0|13.2
--- Comment #6 from Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Kewen Lin changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
--- Comment #5 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
--- Comment #4 from Kewen Lin ---
Starting from r13-5154-g733a1b777f16cd, this failure is gone on Power10 LE (or
with explicit -mcpu=power10), but it shows up on Power8 LE. By checking
r13-5154, this behavior change is expected, the priorities o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
--- Comment #3 from Kewen Lin ---
The attached patch can be bootstrapped and regress-tested and solve the
reported issue right after r13-5107-g6224db0e4d6d3b, but I can not reproduce
the failure with the latest trunk, interesting... I suspected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
--- Comment #2 from Kewen Lin ---
Created attachment 54512
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54512&action=edit
Consider debug insn in no_real_insns_p
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Kewen Lin changed:
What|Removed |Added
Last reconfirmed||2023-02-23
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Peter Bergner changed:
What|Removed |Added
CC||jskumari at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108273
Kewen Lin changed:
What|Removed |Added
CC||bergner at gcc dot gnu.org,
10 matches
Mail list logo