https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116244
Jeffrey A. Law changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
--- Comment #15 from Jeffrey A. Law ---
It's on my list, just higher priority items to deal with right now.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116282
--- Comment #3 from Jeffrey A. Law ---
So yes, this is a problem with the const costing giving two different answers
at different times. That in turn causes the relevant pattern to match at one
point and fail to match at another.
It's a bit of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116244
Jeffrey A. Law changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113035
--- Comment #4 from Jeffrey A. Law ---
Thanks! It actually looks like there's two vsetvls in both output files. But
in the case of the sifive-7 tuning, the two vsetvls set different vector
configurations.
for sifive-7 we have these:
vsetvli
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116389
--- Comment #2 from Jeffrey A. Law ---
Yes, a paradoxical is precisely what we expect and want here. This sounds like
either a reload bug (definitely possible, I'm still chasing one of these over
on the m68k) or a backend bug with avr.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116280
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116282
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116390
--- Comment #7 from Jeffrey A. Law ---
WRT the question in c#1. A paradoxical subreg is the canonical way to say I
want to view this pseudo (or expression) in a mode wider than its native mode
and I don't care about the state of the bits outsid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116389
--- Comment #4 from Jeffrey A. Law ---
I'm pretty confident IRA knows the basics of paradoxicals. The concept of
paradoxicals has been around since the gcc-1 era and Vlad is well aware of how
paradoxicals work.
So while there may be a bug, I d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116389
--- Comment #6 from Jeffrey A. Law ---
Sorry should have written "is _not_ a reasonable assessment" in my prior
message.
RA does assess validity and there's nothing special about avr here and
paradoxicals, unless the backend is doing something
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
--- Comment #16 from Jeffrey A. Law ---
At least part of these are coming from the use-side processing of TImode
operations in carry_backpropagate. The right thing to do in that case is just
return the mode mask indicating all the chunks are po
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
--- Comment #17 from Jeffrey A. Law ---
And the other case is (subreg:SI (reg:TF) 12). No great surprise that the bit
position is problematical for that. Should be an easy fix.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 115876, which changed state.
Bug 115876 Summary: [15 regression] ext-dce.cc has ubsan issues; shifting
negative values
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
What|Removed |
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
Jeffrey A. Law changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116409
Bug ID: 116409
Summary: [15 Regression] Recent phiopt change causing ICE on
riscv64
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
P
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115876
--- Comment #21 from Jeffrey A. Law ---
Just sorry it took so long
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116437
Jeffrey A. Law changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |law at gcc dot gnu.org
--- Comm
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116437
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116420
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116420
--- Comment #3 from Jeffrey A. Law ---
Fun.
The DF framework provides us a way to run dataflow problems on sub-graphs.
Naturally a bitmap of interesting blocks is passed into those routines. At a
confluence point, the DF framework will not m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116420
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116470
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116466
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116466
--- Comment #2 from Jeffrey A. Law ---
Looking at this, I would fully expect that in an optimizing compilation that
the redundant extension would be eliminated. Are you seeing the redundant
sign extensions in the final assembly output or just
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116466
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116466
--- Comment #6 from Jeffrey A. Law ---
Created attachment 59003
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59003&action=edit
Hack from the RAU team
Attached is the hack from the RAU team.
It was initially used to help identify cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116488
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=113939
--- Comment #2 from Jeffrey A. Law ---
Andreas, do you think the m68k port is ready to try bootstrapping with LRA
enabled by default? It'd be relatively simple to flip it in my tester.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113939
--- Comment #4 from Jeffrey A. Law ---
Spinning. Should have some results tomorrow.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116131
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116504
--- Comment #4 from Jeffrey A. Law ---
It's not failing for me, either when using QEMU or when running the resultant
binary on the BPI.
Zdenek, can you (privately) pass along the resulting binary you're testing.
It's pretty easy for me to run
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116152
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115142
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113941
--- Comment #1 from Jeffrey A. Law ---
Not really working on this and I'm not going to lose sleep if this port is
deprecated. But in case someone does care, here's a couple hints.
First the mn103 port will trip an internal consistency check in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116256
Jeffrey A. Law changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116278
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116544
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115921
--- Comment #3 from Jeffrey A. Law ---
IIRC, the reason for that condition to to avoid spoiling certain cases where we
want to ultimately generate shNadd instructions. It's a tradeoff. The shadd
case is probably more important than avoiding th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108039
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116573
Bug ID: 116573
Summary: [15 Regression] Recent SLP work appears to generate
significantly worse code on RISC-V
Product: gcc
Version: 15.0
Status: UNCONFIRMED
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111372
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Resolut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111020
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Sta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110632
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Resolut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109989
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113939
--- Comment #5 from Jeffrey A. Law ---
So the m68k bootstrap with LRA enabled blows up. It looks like the stage1
compiler is mis-compiling the stage2 compiler. The result is a metric ton of
errors building the stage2 libgcc.
A .o bisection la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116488
--- Comment #3 from Jeffrey A. Law ---
*** Bug 116579 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116579
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116615
Bug ID: 116615
Summary: Investigate LOGICAL_OP_NON_SHORT_CIRCUIT for RISC-V
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116662
--- Comment #9 from Jeffrey A. Law ---
So the question in my mind, how important is this? On modern kernels &
toolchains it's possible to query the cboz extension & its block size which
effectively gives you the size of a cache line. But not e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108892
--- Comment #5 from Jeffrey A. Law ---
Right. The fix is a 1-liner. I had it going through a test on x86 and riscv
and lost power. Finally got it re-spun and just need to look at the results.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109040
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108947
--- Comment #2 from Jeffrey A. Law ---
*** Bug 109040 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108892
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109402
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Resolut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109434
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109381
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109104
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108947
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P1
--- Comment #4 from Jeffrey A. Law
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108895
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108360
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108358
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108355
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108351
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108197
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107823
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107270
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106511
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106240
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105834
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105832
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105715
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105628
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109478
--- Comment #2 from Jeffrey A. Law ---
The pa.cc bits look reasonable. It's been forever since I looked at this code,
but clearly using a HOST_WIDE_INT is the right thing to be doing. While it may
not fix this bug completely, consider it pre-a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109027
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107943
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103829
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103637
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103602
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109508
Jeffrey A. Law changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109508
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=108807
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108807
--- Comment #7 from Jeffrey A. Law ---
Once you've committed to the active release branches where this bug is active
(11/12 in this case), you can just close the bug as resolved/fixed. No need to
update the summary/title in that case.
Thanks,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109508
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
--- Comment #4 from Jeffrey A. Law ---
x86's tuning does have some support for avoiding multiple cmovs in a single
if-converted sequence. I'll double check if that's kicking in here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
Jeffrey A. Law changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
--- Comment #6 from Jeffrey A. Law ---
And just an FYI, the tester is flagging conditional move failures for mips64-*
rx-elf and s390-linux-gnu. Most likely these are additional cases where the
hook is indicating the transformation isn't profit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108248
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108247
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106888
--- Comment #4 from Jeffrey A. Law ---
Vineet, we've got some bits here you might want to play with. I'm about to
leave for the evening, but I'll put you in touch with Raphael tomorrow
afternoon.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106888
--- Comment #6 from Jeffrey A. Law ---
Comment on attachment 54905
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54905
proposed patch
So that's a subset of what we've done. We initially thought that was going to
be enough to solve this
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106888
--- Comment #8 from Jeffrey A. Law ---
So coming back to this after a couple months, I'm confident the match.pd change
is unnecessary and in fact wrong. So we definitely want to set that aside.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109592
Bug ID: 109592
Summary: Failure to recognize shifts as sign/zero extension
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106888
--- Comment #10 from Jeffrey A. Law ---
The sign_extend later gets turned into zero_extend. Presumably because we know
the value is never negative. That in and of itself wouldn't be a big deal as
it should be easily recognizable using any_exte
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109592
--- Comment #4 from Jeffrey A. Law ---
If we need to handle subregs here, I would suggest something like this
if (SUBREG_P (XEXP (op0, 0))
&& subreg_lowpart_p (op0)
... other tests ...
That way we know we're extracting the low word of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106585
--- Comment #11 from Jeffrey A. Law ---
Coming back to this.
WRT extension elimination. I've been pondering if we want a late pass to do a
bit of this that can't be handled by REE.
So let's take the case of a Zbs instruction operating on a va
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109549
Jeffrey A. Law changed:
What|Removed |Added
Target|x86_64-*-* |s390
Summary|[14 Regression
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109672
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109721
Bug ID: 109721
Summary: [14 Regression] predcom-2 fails after recent changes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Compon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109776
Bug ID: 109776
Summary: [14 Regression] pr81192 fails on some targets after
recent propagator changes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity:
601 - 700 of 1404 matches
Mail list logo