https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109777
Bug ID: 109777
Summary: [14 regression] Compare-debug failure after recent
changes
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Pr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109776
--- Comment #7 from Jeffrey A. Law ---
Thanks. That took care of the xstormy16 issues.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109777
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #4 from Jeffrey A. Law
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109592
--- Comment #6 from Jeffrey A. Law ---
I would still rather not introduce special cases for SUBREGs if we can avoid
it. I think the question remains whether or not patching simplify-rtx's
canonicalize_shift is sufficient to fix this problem (pe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109848
Bug ID: 109848
Summary: [14 Regression] Recent change causing testsuite ICE on
csky port
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114511
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114591
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114559
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114545
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114415
Jeffrey A. Law changed:
What|Removed |Added
Summary|[13/14 Regression] wrong|[13 Regression] wrong code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114415
--- Comment #9 from Jeffrey A. Law ---
Yea. I think my first one in this space was in the mid 90s on the PA. Sigh.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113742
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Resolut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84568
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89835
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Stat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114676
Jeffrey A. Law changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114689
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114634
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114621
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114608
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Sta
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112723
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729
Jeffrey A. Law changed:
What|Removed |Added
Last reconfirmed||2024-04-15
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729
--- Comment #7 from Jeffrey A. Law ---
Yes, there are different algorithms. I looked at them a while back when we
first noticed the problems with spilling and x264. There was very little
difference for specint when we varied the algorithms. I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729
--- Comment #8 from Jeffrey A. Law ---
I didn't even notice you had that testcase attached!
I haven't done a deep dive, but the first thing that jumps out is the number of
instructions in the ready queue, most likely because of the addressing o
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114741
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114709
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114677
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113956
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113291
Jeffrey A. Law changed:
What|Removed |Added
Priority|P1 |P2
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114729
--- Comment #11 from Jeffrey A. Law ---
Yup. -fsched-verbose=99 is *very* verbose. But that's the point, to see all
the gory details. It can be dialed down, but I've never done so myself.
What stands out to me is this:
;;| Pressure co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114787
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114506
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114885
Jeffrey A. Law changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114996
Bug ID: 114996
Summary: [15 Regression] [RISC-V] 2->2 combination no longer
occurring
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114996
--- Comment #2 from Jeffrey A. Law ---
I don't care about the terminology. We have 3 insns in play. A, B and C.
We try to combine A -> B which succeeded before resulting in A, B' and C and
which in turn allowed a subsequent A -> C combination
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115017
Bug ID: 115017
Summary: [15 Regression] Ranger ICE
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115013
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Tar
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115009
Jeffrey A. Law changed:
What|Removed |Added
Target|avr |avr, rl78
--- Comment #5 from Jeffrey
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115009
--- Comment #8 from Jeffrey A. Law ---
And on msp430-elf we're getting a codegen correctness issue on msp430-elf.
gcc.dg/pr66444.c fails in the simulator. The -O2 code difference looks like:
*** good.s Thu May 9 20:41:37 2024
--- bad.s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115026
--- Comment #7 from Jeffrey A. Law ---
So what's the magic to re-enable prange? I can do that and spin a fresh build.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115013
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115013
--- Comment #5 from Jeffrey A. Law ---
So this seems to have fixed the RISC-V port. Thanks!
I'm still seeing some problems on the PRU port though:
Tests that now fail, but worked before (1 tests):
pru-sim: gcc: gcc.dg/pr71478.c (test for exc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92539
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
--- Comment #12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115110
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=115123
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115142
--- Comment #2 from Jeffrey A. Law ---
So just one high level note. Nobody is ever going to do something like
"-ftree-ter" without having one of the optimization levels on. It's an option
combination that just doesn't make sense.
But we still
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115142
Jeffrey A. Law changed:
What|Removed |Added
Last reconfirmed||2024-05-18
Status|UNCONFIR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115142
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115142
--- Comment #5 from Jeffrey A. Law ---
Yes, sorry. I should have removed the 15 tag.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115038
--- Comment #8 from Jeffrey A. Law ---
Yea, I would think we want to avoid anything marked as frame related.
Otherwise we have to go back and fixup the CFI nodes and such.
Eric, do you want to handle the final bootstrap+regression test? Or do
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115220
Jeffrey A. Law changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
Bug ID: 115298
Summary: [15 Regression] Various targets failing DSE tests
after recent changes
Product: gcc
Version: 15.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
--- Comment #2 from Jeffrey A. Law ---
What still doesn't make sense is why nds32 would be special here. It doesn't
do anything special with flag_delete_null_pointer_checks and I don't think it
uses any of the address space hooks. So why does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
--- Comment #4 from Jeffrey A. Law ---
Agh. I was looking in the main config directory, not common/config. So it all
makes sense now.
So if we go back to your original analysis, I think we can say things are
behaving correctly and we just nee
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115298
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114996
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114996
Jeffrey A. Law changed:
What|Removed |Added
Priority|P4 |P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113357
--- Comment #11 from Jeffrey A. Law ---
That's not the way we do things. And my bootstraps on m68k are working fine.
Last one was 6 days ago.
This needs to be debugged by someone with the time/interest on the m68k.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111777
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111777
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111798
Bug ID: 111798
Summary: [14 Regression] Recent change causing testsuite
regression and poor code on mcore-elf
Product: gcc
Version: unknown
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111466
Jeffrey A. Law changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107885
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Resolut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112298
Bug ID: 112298
Summary: Poor code for DImode operations on H8 port
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: targe
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112298
Jeffrey A. Law changed:
What|Removed |Added
Target||h8300
Priority|P3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112320
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112320
--- Comment #6 from Jeffrey A. Law ---
Created attachment 56480
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56480&action=edit
Testcase for fr30-elf -Os -g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104387
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=109035
--- Comment #8 from Jeffrey A. Law ---
No spills on rv64 either.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111311
--- Comment #14 from Jeffrey A. Law ---
As Andrew said, if there's a test that depends on behavior of -INT_MIN, then
the test needs to be fixed. That's undefined behavior.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #6 from Jeffrey A. Law ---
Do we have assembly code around the faulting point (x/20i $pc) and a register
dump (i r)? The biggest concern I'd have with f-m-o on the PA would be the
implicit segment selection that happens on the base
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #19 from Jeffrey A. Law ---
f-m-o runs post-allocation, so the scope of where it's behavior can change
things is narrower. So testing with -fno-schedule-insns isn't going to be
useful, but -fno-schedule-insns2 might.
I'm a bit conc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
--- Comment #26 from Jeffrey A. Law ---
As a compiler junkie, I tend to think compiler first until I can prove it
otherwise. I wouldn't get too hung up on aliasing issues and such at this
point.
Do we already have a dump for the key function?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112462
Bug ID: 112462
Summary: RISC-V zicond cost model enhancements
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112468
Bug ID: 112468
Summary: [14 Regression] Missed phi-opt after recent change
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Componen
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?
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=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=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=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=112478
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
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 #11
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112530
Bug ID: 112530
Summary: [14 Regression] New ICE in gimple->rtl expansion after
recent change
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
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. ***
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=112674
Bug ID: 112674
Summary: [14 Regression] Compare-debug failure after recent
change on c6x
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112848
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106888
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109592
--- Comment #7 from Jeffrey A. Law ---
Attached is what I cobbled together. It doesn't use magic numbers. But it
doesn't yet handle zero extensions in the simplify-rtx code. But I think it
shows the overall direction fairly well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108041
--- Comment #3 from Jeffrey A. Law ---
Created attachment 55185
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55185&action=edit
(Incomplete) Patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109592
--- Comment #9 from Jeffrey A. Law ---
Weird, I don't see the attachment either. I'll extract & upload it again.
WRT costing. fwprop and combine will both query the target rtx costs and will
reject when the target costing model indicates the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108041
--- Comment #4 from Jeffrey A. Law ---
Patch was for a different problem. Sorry.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109592
--- Comment #10 from Jeffrey A. Law ---
Created attachment 55218
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55218&action=edit
(Incomplete) Patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110109
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110163
Bug ID: 110163
Summary: [14 Regression] Comparing against a constant string is
inefficient on some targets
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Sever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110163
--- Comment #2 from Jeffrey A. Law ---
It is a regression for rv64. So probably P4 would be most appropriate.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110218
--- Comment #2 from Jeffrey A. Law ---
So what I think was happening was that we would sink past a bunch of
conditionals that were never going to be true thinking that we were moving to a
deeper control nest. So the idea was to use the frequenc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79173
--- Comment #23 from Jeffrey A. Law ---
risc-v doesn't have any special instructions to implement add-with-carry or
subtract-with-borrow. Depending on who you talk do, it's either a feature or a
mis-design.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110264
Jeffrey A. Law changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
701 - 800 of 1404 matches
Mail list logo