https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96298
Roger Sayle changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
||roger at nextmovesoftware dot
com
Resolution|--- |FIXED
--- Comment #6 from Roger Sayle ---
Fixed. Thanks for everyone's help. Sorry again.
||roger at nextmovesoftware dot
com
Status|UNCONFIRMED |RESOLVED
--- Comment #3 from Roger Sayle ---
Fixed, and a test case added to ensure this doesn't happen again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61494
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
||roger at nextmovesoftware dot
com
Status|NEW |RESOLVED
Target Milestone|--- |10.0
--- Comment #17 from Roger Sayle ---
Fixed on mainline and the gcc-10 branch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97978
--- Comment #2 from Roger Sayle ---
The -fno-PIC isn't required, as -Os alone is sufficient to trigger this ICE.
I'm not sure if unconditionally calling __builtin_unreachable qualifies as
"valid-code" (or possibly an error condition) but lra_assi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98713
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
||roger at nextmovesoftware dot
com
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98713
--- Comment #7 from Roger Sayle ---
I agree in the general case, a conditional jump (that depends only on the
condition flags) potentially has a shorter dependence chain than a cmov (which
depends on the condition flags and two registers). But i
||roger at nextmovesoftware dot
com
Target Milestone|--- |7.0
Status|UNCONFIRMED |RESOLVED
--- Comment #5 from Roger Sayle ---
This issue has been fixed since gcc 7; the compiler now stores the high-byte
register ah/bh/dh etc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100810
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46235
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
|RESOLVED
CC||roger at nextmovesoftware dot
com
Resolution|--- |FIXED
--- Comment #2 from Roger Sayle ---
GCC now generates a single lea instruction for both examples (as confirmed by
the link to godbolt
||roger at nextmovesoftware dot
com
Resolution|--- |FIXED
Target Milestone|--- |4.6.4
--- Comment #8 from Roger Sayle ---
GCC generates code without shifts for all the examples in comment #4, since
around version 4.6.4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19986
Bug 19986 depends on bug 20517, which changed state.
Bug 20517 Summary: bit shift/mask optimization potential
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20517
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108229
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106704
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107991
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
||roger at nextmovesoftware dot
com
--- Comment #9 from Roger Sayle ---
This has been fixed for GCC 12 and GCC 13. Thanks to Vladimir.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105546
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
|--- |13.0
CC||roger at nextmovesoftware dot
com
Resolution|--- |FIXED
--- Comment #5 from Roger Sayle ---
This should now be fixed on mainline.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92342
Roger Sayle changed:
What|Removed |Added
Summary|[10/11/12/13 Regression] a |[10/11/12 Regression] a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594
--- Comment #10 from Roger Sayle ---
Status update: The x86 backend pieces of my proposed fix have been approved and
committed, but the remaining middle-end pieces have been making slow progress:
https://gcc.gnu.org/pipermail/gcc-patches/2023-Ja
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594
--- Comment #14 from Roger Sayle ---
This really is a regression, that points to a previously latent/unnoticed bug
in combine.
In GCC 12, combine would take the input RTL and based on target costs transform
it into the better of implementation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594
--- Comment #15 from Roger Sayle ---
An example of combine's temporary lapses of sanity can be seen on powerpc:
Trying 14 -> 15:
14: %3:SI=sign_extend(r128:SI#2)*sign_extend(r127:SI#2)
REG_DEAD r128:SI
REG_DEAD r127:SI
15: use
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594
--- Comment #21 from Roger Sayle ---
I completely agree that Richard Sandiford's patch is a much better solution,
but I'd like to counter the claims that the change originally proposed in
comment #8 is obviously universally bad.
Segher has prop
||roger at nextmovesoftware dot
com
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
Keywords||patch
--- Comment #28 from Roger Sayle ---
Doh! My apologies for this breakage. I'm currently te
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103354
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106594
Roger Sayle changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109031
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109104
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
||2022-02-20
Status|UNCONFIRMED |ASSIGNED
CC||roger at nextmovesoftware dot
com
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
--- Comment #1 from Roger Sayle ---
Patch
||roger at nextmovesoftware dot
com
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
--- Comment #2 from Roger Sayle ---
Patch proposed.
https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590653.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96442
Roger Sayle changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
|--- |FIXED
Target Milestone|--- |12.0
CC||roger at nextmovesoftware dot
com
--- Comment #9 from Roger Sayle ---
This is fixed on mainline; the godbolt link in comment #1 shows that GCC now
generates the same code
||roger at nextmovesoftware dot
com
Resolution|--- |FIXED
Target Milestone|9.5 |12.0
--- Comment #17 from Roger Sayle ---
This appears to have been fixed on trunk; a cross-compiler to sh-elf produces:
_test000:
mov
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95126
Roger Sayle changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39751
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80270
Roger Sayle changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
gcc dot gnu.org |roger at
nextmovesoftware dot com
CC||roger at nextmovesoftware dot
com
--- Comment #14 from Roger Sayle ---
Patch proposed.
https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590961.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100536
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84964
Roger Sayle changed:
What|Removed |Added
CC||cnsun at uwaterloo dot ca
--- Comment #15
||roger at nextmovesoftware dot
com
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
--- Comment #15 from Roger Sayle ---
Patch proposed.
https://gcc.gnu.org/pipermail/gcc-patches/2022-February/591013.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80270
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|9.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91384
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone|9.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104345
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104732
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
||roger at nextmovesoftware dot
com
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Roger Sayle ---
This should be fixed on mainline for GCC 12.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98335
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
||roger at nextmovesoftware dot
com
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
--- Comment #4 from Roger Sayle ---
Patch proposed.
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591291.html
||roger at nextmovesoftware dot
com
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
--- Comment #3 from Roger Sayle ---
Patch proposed.
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591292.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96440
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96329
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|11.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96437
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96440
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104732
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39751
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target Milestone|9.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95999
Roger Sayle changed:
What|Removed |Added
Target Milestone|9.5 |12.0
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98420
Roger Sayle changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
at gcc dot gnu.org |roger at
nextmovesoftware dot com
CC||roger at nextmovesoftware dot
com
--- Comment #5 from Roger Sayle ---
Patch proposed.
https://gcc.gnu.org/pipermail/gcc-patches/2022-March/591644.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78249
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51446
Roger Sayle changed:
What|Removed |Added
CC||joshua.england@worldprogram
||2022-03-12
CC||roger at nextmovesoftware dot
com
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
--- Comment #1 from Roger Sayle ---
Patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98420
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98335
Roger Sayle changed:
What|Removed |Added
Target Milestone|9.5 |12.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101895
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 101895, which changed state.
Bug 101895 Summary: [11/12 Regression] SLP Vectorizer change pushes
VEC_PERM_EXPR into bad location spoiling further optimization opportunities
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101
nextmovesoftware dot com |unassigned at gcc dot
gnu.org
Resolution|--- |FIXED
--- Comment #15 from Roger Sayle ---
Unassigning myself (in case anyone wants to backport this fix themselves).
|--- |FIXED
CC||roger at nextmovesoftware dot
com
Status|NEW |RESOLVED
--- Comment #7 from Roger Sayle ---
This has been fixed since Hongtao's patch last year. But the single
remaining case has now been
||roger at nextmovesoftware dot
com
Resolution|--- |FIXED
Status|NEW |RESOLVED
--- Comment #8 from Roger Sayle ---
This has now been fixed on mainline.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105034
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105034
--- Comment #5 from Roger Sayle ---
The latest CSiBE results on x86_64-pc-linux-gnu: With -Os the total size is
3696263, and with -Os -mno-stv the total size is 3966887, i.e. 624 bytes
larger. The worst regression from -mno-stv is
teem-1.6.0-s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104885
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84964
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70321
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
|RESOLVED
CC||roger at nextmovesoftware dot
com
Target Milestone|--- |4.5.4
--- Comment #3 from Roger Sayle ---
I agree with Andrew Pinski that the issue with this test case (conditional
return vs. cross-jumping
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16996
Bug 16996 depends on bug 40361, which changed state.
Bug 40361 Summary: Conditional return not always profitable with -Os
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40361
What|Removed |Added
--
at gcc dot gnu.org |roger at
nextmovesoftware dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106347
Roger Sayle changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106303
Roger Sayle changed:
What|Removed |Added
CC||zsojka at seznam dot cz
--- Comment #7 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106404
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106303
--- Comment #8 from Roger Sayle ---
*** Bug 106407 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106407
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106303
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106347
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106447
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
at gcc dot gnu.org |roger at
nextmovesoftware dot com
--- Comment #3 from Roger Sayle ---
I'm bootstrapping and regression testing a fix now.
||2022-07-30
Status|UNCONFIRMED |ASSIGNED
CC||roger at nextmovesoftware dot
com
Ever confirmed|0 |1
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware
|UNCONFIRMED |NEW
CC||roger at nextmovesoftware dot
com
Ever confirmed|0 |1
--- Comment #5 from Roger Sayle ---
I see the same problem, building out of the source tree on x86_64-pc-linux-gnu
with GNU make 3.82. I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #7 from Roger Sayle ---
At the point that this fails there is no
/home/roger/GCC/clean_go/x86_64-pc-linux-gnu/libbacktrace directory whilst
the build (make) is in /home/roger/GCC/clean_go/x86_64-pc-linux-gnu/libgo
I also don't use an
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #8 from Roger Sayle ---
Investigating further, using an absolute path doesn't help, but interestingly
after the failure, repeatedly trying "make -j 8 bootstrap" a few times, allows
the build to progress after several attempts, so it
|ASSIGNED
Assignee|unassigned at gcc dot gnu.org |roger at
nextmovesoftware dot com
--- Comment #11 from Roger Sayle ---
Patch proposed:
https://gcc.gnu.org/pipermail/gcc-patches/2022-July/599095.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106450
Roger Sayle changed:
What|Removed |Added
CC||zsojka at seznam dot cz
--- Comment #4 fr
|--- |13.0
CC||roger at nextmovesoftware dot
com
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Roger Sayle ---
This is a duplicate of PR target/106450, and (will be) fixed resolved by the
patch posted here
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106450
Roger Sayle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106481
Roger Sayle changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
: enhancement
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: roger at nextmovesoftware dot com
Target Milestone: ---
This enhacement request is a proposal for improving/tweaking GCC's register
allocation, but assuming/m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47949
Roger Sayle changed:
What|Removed |Added
CC||roger at nextmovesoftware dot
com
||roger at nextmovesoftware dot
com
Status|NEW |RESOLVED
Target Milestone|--- |13.0
--- Comment #3 from Roger Sayle ---
This has now been fixed on mainline (for both scalar and vector types). Thanks
Sam.
1 - 100 of 427 matches
Mail list logo