||law at gcc dot gnu.org
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
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113956
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=114741
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
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
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.
|UNCONFIRMED |NEW
Ever confirmed|0 |1
CC||law at gcc dot gnu.org
--- Comment #3 from Jeffrey A. Law ---
Right. So what I'm most interested in are the scheduler decisions as most
likely IRA/LRA are simply stuck
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112723
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114608
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=114689
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
||law at gcc dot gnu.org
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed||2024-04-12
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89835
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84568
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113742
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
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=114415
Jeffrey A. Law changed:
What|Removed |Added
Summary|[13/14 Regression] wrong|[13 Regression] wrong code
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114591
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114511
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114515
--- Comment #9 from Jeffrey A. Law ---
Thanks for that info Edwin -- my tester flagged them too and mentally I'd
figured it was most likely the combiner change.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114393
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
||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=114510
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=101463
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102264
Jeffrey A. Law changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104995
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105275
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=106955
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107058
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 108278, which changed state.
Bug 108278 Summary: [13/14 Regression] runtime error with -O1 -Wall
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108278
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108278
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=113357
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #5 from Jeffrey A. Law
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109990
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110285
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110401
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110842
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=111231
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111305
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P2
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112415
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
||law at gcc dot gnu.org
||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 112697, which changed state.
Bug 112697 Summary: [14 Regression] 30-40% exec time regression of 433.milc on
zen2 since r14-4972-g8aa47713701b1f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112697
What
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112697
Jeffrey A. Law changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114426
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=114408
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=114414
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113390
--- Comment #4 from Jeffrey A. Law ---
Made it a P1 simply because it was likely not RISC-V specific ICE. I don't
think we're at a point where it makes sense for RISC-V to be a primary
platform, though hopefully that'll change in the
|--- |FIXED
CC||law at gcc dot gnu.org
--- Comment #5 from Jeffrey A. Law ---
Per c#4.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89180
Bug 89180 depends on bug 56457, which changed state.
Bug 56457 Summary: Bogus warning: loop-invariant.c:786:20: error: unused
variable ‘regno’ when building vax-*-*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56457
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44756
Bug 44756 depends on bug 56457, which changed state.
Bug 56457 Summary: Bogus warning: loop-invariant.c:786:20: error: unused
variable ‘regno’ when building vax-*-*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56457
What|Removed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112703
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=113359
--- Comment #20 from Jeffrey A. Law ---
Go right ahead. I'm mostly trying to get things in the right broad buckets.
So if you've got additional information, please add it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113359
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=113727
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114269
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114303
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114304
Jeffrey A. Law changed:
What|Removed |Added
Priority|P3 |P4
||law at gcc dot gnu.org
|use-after-free warning |use-after-free warning
|triggered by optimizer |triggered by optimizer
CC||law at gcc dot gnu.org
--- Comment #7 from Jeffrey A. Law ---
Works with gcc-13 and the trunk. Adjusting regression
CC| |law at gcc dot gnu.org
--- Comment #11 from Jeffrey A. Law ---
Adjusting regression markers per c#10.
||law at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #12 from Jeffrey A. Law ---
Per c#8 and c#10.
]
|Incorrect "writing 1 byte |Incorrect "writing 1 byte
|into a region of size 0" on |into a region of size 0" on
|a vectorized loop |a vectorized loop
CC| |law at gcc dot gnu.org
--- Com
|misleading warning :|warning : iteration X
|iteration X invokes |invokes undefined behavior
|undefined behavior |
CC||law at gcc dot gnu.org
--- Comment #8 from Jeffrey A. Law
-gece28da924ddda8b |r12-3300-gece28da924ddda8b
CC||law at gcc dot gnu.org
--- Comment #4 from Jeffrey A. Law ---
False positive is fixed w/ gcc-13 and the trunk.
]
|std::variant triggers |...> triggers
|false-positive 'may be used |false-positive 'may be used
|uninitialized' warning |uninitialized' warning
CC| |law at gcc dot gnu.org
--- Comment #14 from Jeff
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112548
--- Comment #25 from Jeffrey A. Law ---
Well, at least in theory SPEC isn't supposed to be changing the sources or
validation criteria on us. So while our copy may be old, I would expect it's
still the same as Filip's.
That doesn't resolve
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114304
--- Comment #18 from Jeffrey A. Law ---
I don't have an opinion on the Fortran patch -- I think it's up to the Fortran
front-end maintainers to make that decision.
Given there's still a regression here, I'll put the marker back.
|libgfortran I/O – bogus |"Semicolon not allowed as
|"Semicolon not allowed as |separator with
|separator with |DECIMAL='point'"
|DECIMAL='point'"|
CC|
||law at gcc dot gnu.org
||law at gcc dot gnu.org
|r217828 prevents RTL loop |prevents RTL loop unroll
|unroll |
CC||law at gcc dot gnu.org
--- Comment #70 from Jeffrey A. Law ---
Per c#68. Given there's been ~6 years since any significant work was done
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114261
--- Comment #7 from Jeffrey A. Law ---
Yea, there are various limits on the size of various lists the scheduler
maintains. This looks independent of those various clamps.
]
|tree-ifcombine aarch64 |tree-ifcombine aarch64
|performance regression with |performance regression with
|trunk@245151|trunk@245151
CC||law at gcc dot gnu.org
--- Comment #23 from Jeffrey A. Law
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80491
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80899
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
1 - 100 of 1154 matches
Mail list logo