https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #16 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:3fd32d3d22d86ab732b9b997bdabe449b8c53bbe
commit r14-8180-g3fd32d3d22d86ab732b9b997bdabe449b8c53bbe
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #15 from Anonymous ---
(In reply to Andrew Pinski from comment #10)
> (In reply to Anonymous from comment #9)
> > (In reply to Andrew Pinski from comment #1)
> > > dom3 :
> > > ```
> >
> > Could you please explain on how you to reco
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
Andrew Macleod changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #13 from Jakub Jelinek ---
r14-2097-g4dfeb1cd8dfca234186216d891ec8f46235c3a14
was a trunk commit, was that backported to 13 branch too (or was it fixed there
some other way)?
In any case, guess we should include the testcase into the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
Andrew Macleod changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #11 from Andrew Macleod ---
(In reply to Andrew Pinski from comment #10)
> (In reply to Anonymous from comment #9)
> > (In reply to Andrew Pinski from comment #1)
> > > dom3 :
> > > ```
> >
> > Could you please explain on how you to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #10 from Andrew Pinski ---
(In reply to Anonymous from comment #9)
> (In reply to Andrew Pinski from comment #1)
> > dom3 :
> > ```
>
> Could you please explain on how you to record this trace? Is there any
> specific compilation op
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
Anonymous changed:
What|Removed |Added
CC||iamanonymous.cs at gmail dot
com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
Richard Biener changed:
What|Removed |Added
Target Milestone|13.2|13.3
--- Comment #8 from Richard Biene
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #7 from Andrew Macleod ---
(In reply to Andrew Macleod from comment #6)
> bah.
>
> Ranger hang is resolved with:
>
> commit 4dfeb1cd8dfca234186216d891ec8f46235c3a14
> Date: Thu Jun 22 10:00:12 2023 -0400
>
> Avoid redundan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #6 from Andrew Macleod ---
bah.
Ranger hang is resolved with:
commit 4dfeb1cd8dfca234186216d891ec8f46235c3a14
Date: Thu Jun 22 10:00:12 2023 -0400
Avoid redundant GORI calcualtions.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
--- Comment #5 from Andrew Macleod ---
hmm. yeah. its triggering some kind of pathological edge evaluation between
GORI and cache updating.
There is a long sequence of dependent stmts, presumably the unrolled loop, and
a sequential series of co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
Jakub Jelinek changed:
What|Removed |Added
CC||aldyh at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
Jakub Jelinek changed:
What|Removed |Added
CC||andrew.carlotti at arm dot com,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110251
Andrew Pinski changed:
What|Removed |Added
Keywords||needs-bisection
Known to fail|
16 matches
Mail list logo
