https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115333
--- Comment #2 from Kostadin Shishmanov ---
I suppose we can close this then?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115333
Bug ID: 115333
Summary: -march=native sets --param "l2-cache-size=1024" on
Ryzen 7 7800X3D
Product: gcc
Version: 14.1.1
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810
--- Comment #1 from Kostadin Shishmanov ---
Created attachment 58011
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58011&action=edit
reduced testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114810
Bug ID: 114810
Summary: [14 Regression] internal compiler error: in
lra_split_hard_reg_for, at lra-assigns.cc:1868
(unable to find a register to spill)
{*andndi3_d
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112634
Kostadin Shishmanov changed:
What|Removed |Added
CC||kocelfc at tutanota dot com
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112619
Kostadin Shishmanov changed:
What|Removed |Added
CC||jason at redhat dot com
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112619
Kostadin Shishmanov changed:
What|Removed |Added
CC||kocelfc at tutanota dot com
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
--- Comment #18 from Kostadin Shishmanov ---
(In reply to Andrew Pinski from comment #17)
> Can you try the patch in
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112572#c18 ?
The patch does fix it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
Kostadin Shishmanov changed:
What|Removed |Added
Attachment #56602|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
Kostadin Shishmanov changed:
What|Removed |Added
Attachment #56603|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
Kostadin Shishmanov changed:
What|Removed |Added
Attachment #56614|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
Kostadin Shishmanov changed:
What|Removed |Added
Attachment #56613|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
--- Comment #11 from Kostadin Shishmanov ---
I think the gcc builds might be a bit more different than just the commit
reverted, so I am going to redo everything and upload the attachments again
with just that difference.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
--- Comment #10 from Kostadin Shishmanov ---
Created attachment 56614
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56614&action=edit
dump of the first bad pass with the commit reverted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
--- Comment #9 from Kostadin Shishmanov ---
Created attachment 56613
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56613&action=edit
dump of the first bad pass with the problematic commit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
--- Comment #7 from Kostadin Shishmanov ---
Created attachment 56612
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56612&action=edit
bad object file
I've attached the bad object file (the one from the compilation with the "bad"
commit).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
Kostadin Shishmanov changed:
What|Removed |Added
CC||kocelfc at tutanota dot com
--- C
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
--- Comment #2 from Kostadin Shishmanov ---
Created attachment 56604
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56604&action=edit
preprocessed files compressed with xz -9e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
--- Comment #1 from Kostadin Shishmanov ---
Created attachment 56603
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56603&action=edit
objdump -d -Mintel of function with the commit reverted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112568
Bug ID: 112568
Summary: [14 Regression] Miscompilation of radeonsi (mesa) with
-march=raptorlake (-mavx) since
r14-5355-g3cd3a09b3f91a1
Product: gcc
Version: 14.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
--- Comment #6 from Kostadin ---
(In reply to Andrew Pinski from comment #5)
> (In reply to Kostadin from comment #4)
> > This is the first commit where it doesn't ICE. I reverted it from master,
> > and it did start ICEing again.
>
> Does the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112381
--- Comment #4 from Kostadin ---
This is the first commit where it doesn't ICE. I reverted it from master, and
it did start ICEing again.
commit r14-5001-g8111b5c23bd14f
Author: Haochen Gui
Date: Mon Oct 30 10:59:51 2023 +0800
Expand: C
22 matches
Mail list logo