https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113441
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113505
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113525
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
|RESOLVED
CC||law at gcc dot gnu.org
--- Comment #5 from Jeffrey A. Law ---
Should be fixed on the trunk now.
||law at gcc dot gnu.org
||law at gcc dot gnu.org
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113618
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113641
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
|1
Priority|P3 |P1
CC||law at gcc dot gnu.org
Status|UNCONFIRMED |NEW
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113724
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113752
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113847
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113996
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114151
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114261
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108792
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110199
Jeffrey A. Law changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113738
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113738
Jeffrey A. Law changed:
What|Removed |Added
Last reconfirmed||2024-03-06
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109760
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109760
Jeffrey A. Law changed:
What|Removed |Added
Last reconfirmed||2024-03-06
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113001
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113001
--- Comment #3 from Jeffrey A. Law ---
*** Bug 112871 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112871
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114221
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110369
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110390
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
|RESOLVED
CC||law at gcc dot gnu.org
--- Comment #10 from Jeffrey A. Law ---
Fixed on the trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110841
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110942
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113575
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84402
Bug 84402 depends on bug 113575, which changed state.
Bug 113575 Summary: [14 Regression] memory hog building insn-opinit.o
(i686-linux-gnu -> riscv64-linux-gnu)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113575
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112301
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112871
Jeffrey A. Law changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |law at gcc dot gnu.org
|RESOLVED
CC||law at gcc dot gnu.org
--- Comment #5 from Jeffrey A. Law ---
Should be fixed on the trunk now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113001
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113226
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113384
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113533
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113575
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113790
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113790
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Last
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114000
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114000
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100523
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112758
--- Comment #19 from Jeffrey A. Law ---
Fixed by Jakub's patch on the trunk.
||law at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #11 from Jeffrey A. Law ---
Fixed by Greg's patch on the trunk. No current plans to backport.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113976
--- Comment #3 from Jeffrey A. Law ---
What does the standard say about changing const objects?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84201
Jeffrey A. Law changed:
What|Removed |Added
CC||vineetg at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 113570, which changed state.
Bug 113570 Summary: RISC-V: SPEC2017 549 fotonik3d miscompilation in autovec
VLS 256 build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113570
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113570
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113570
--- Comment #3 from Jeffrey A. Law ---
See pr84201 for more details as well as
https://www.spec.org/cpu2017/Docs/benchmarks/549.fotonik3d_r.html
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: law at gcc dot gnu.org
Target Milestone: ---
sh3-linux-gnu or sh3eb-linux-gnu is showing a code generation regression after
the changes for pr111267.
test_01 with -O1
|--- |FIXED
Target Milestone|--- |14.0
CC||law at gcc dot gnu.org
--- Comment #8 from Jeffrey A. Law ---
Fixed on the trunk. No plans to backport.
||law at gcc dot gnu.org
Resolution|--- |FIXED
Target Milestone|--- |14.0
--- Comment #7 from Jeffrey A. Law ---
Should be fixed on the trunk. No plans to backport.
||law at gcc dot gnu.org
Status|NEW |RESOLVED
--- Comment #9 from Jeffrey A. Law ---
Fixed on the trunk. No plans to backport.
||law at gcc dot gnu.org
Status|NEW |RESOLVED
--- Comment #14 from Jeffrey A. Law ---
Fixed on the trunk. No plans to backport.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113399
--- Comment #4 from Jeffrey A. Law ---
Just something that was missed when this option was changed from target
dependent to target independent. It definitely should not be a target option.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112398
--- Comment #5 from Jeffrey A. Law ---
I don't think we need to do any significant bit tracking to optimize the
original neg8 test. I think we can be handled entirely within the simplify-rtx
framework.I've got a junior engineer that's going
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112398
Jeffrey A. Law changed:
What|Removed |Added
Last reconfirmed|2023-11-05 00:00:00 |2024-01-13
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111378
--- Comment #4 from Jeffrey A. Law ---
Whether or not this is an optimization or a pessimization is dependent on the
target -- some targets can express the constant trivially in a branch
conditions, others can not. Some targets have barrel shif
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113167
--- Comment #7 from Jeffrey A. Law ---
So far that's the only fallout I've seen on the embedded targets.
The qemu emulated natives aren't running as I've got some kind of network
problem here and the workers are going offline after a few hours
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: law at gcc dot gnu.org
Target Milestone: ---
Many targets are now seeing this failure:
FAIL: gcc.dg/tree-ssa/gen-vect-26.c scan-tree-dump
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110201
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
|RESOLVED
CC||law at gcc dot gnu.org
--- Comment #9 from Jeffrey A. Law ---
Fixed on the trunk. No plans to backport.
||2023-12-04
Ever confirmed|0 |1
CC||law at gcc dot gnu.org
--- Comment #2 from Jeffrey A. Law ---
Also seeing on microblaze-linux.
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: law at gcc dot gnu.org
Target Milestone: ---
This patch:
commit 6bf66276e3e41d5d92f7b7260e98b6a111653805
Author: Richard Biener
Date: Wed Nov 22 11:10:41 2023 +0100
tree
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112674
--- Comment #1 from Jeffrey A. Law ---
And possibly more interesting than the compare-debug failure is this patch
seems to be causing Wstringop-overflow-17 to fail on multiple targets,
including c6x.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112530
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112481
--- Comment #14 from Jeffrey A. Law ---
*** Bug 112530 has been marked as a duplicate of this bug. ***
mal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: law at gcc dot gnu.org
Target Milestone: ---
This change:
commit a5922427c29fad177251d89cc946d1c5bfc135eb
Author: Andrew Stubbs
Date: Fri Oct 20 16:26:51 2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112481
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112478
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #43 from Jeffrey A. Law ---
I would expect allowing larger offsets before reload to be a significant
problem.
The core issue is integer memory operations allow 14 bits while FP only allows
5. During reloading we don't know if any g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112497
--- Comment #5 from Jeffrey A. Law ---
This failure means the stage1 and stage2 compilers generated different code for
the same input.
So when I need to debug this I usually start by first getting that source code.
Based in the title of this b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112497
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #41 from Jeffrey A. Law ---
I would agree. In fact,the whole point of the f-m-o pass is to bring those
immediates into the memory reference. It'd be really useful to know why that
isn't happening.
The only thing I can think of wou
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #31 from Jeffrey A. Law ---
IIRC r21 is call-clobbered. So I guess the question turns into what was the
sequence before f-m-o got involved -- was it assuming r21 would be preserved,
or did f-m-o make r21 live across the call?
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: law at gcc dot gnu.org
Target Milestone: ---
This change:
commit 3f176e1adc6bc9cc2c21222d776b51d9f43cb66b (HEAD)
Author: Tamar Christina
Date: Thu Nov 9 13:59:39 2023 +
middle-end: optimize
501 - 600 of 1354 matches
Mail list logo