Bug 2043246 - gcc12: internal compiler error on ppc64le when compiling gnuradio
Summary: gcc12: internal compiler error on ppc64le when compiling gnuradio
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2045122
TreeView+ depends on / blocked
 
Reported: 2022-01-20 21:28 UTC by Jaroslav Škarvada
Modified: 2022-01-28 14:02 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-01-28 14:02:05 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Škarvada 2022-01-20 21:28:08 UTC
Description of problem:
https://kojipkgs.fedoraproject.org//work/tasks/146/81550146/build.log

Version-Release number of selected component (if applicable):
gcc-c++-12.0.1-0.2.fc36

How reproducible:
Try to compile gnuradio package on the ppc64le

Steps to Reproduce:
1. Clone gnuradio
2. fedpkg scratch-build
3.

Actual results:
Internal compiler error

Expected results:
No internal compiler error

Additional info:
Koji task:
https://koji.fedoraproject.org/koji/taskinfo?taskID=81550146

Comment 1 Mattia Verga 2022-01-22 15:06:37 UTC
The same happens for kpmcore:
https://kojipkgs.fedoraproject.org//work/tasks/6/81530006/build.log

Possible duplicate: #2042668

Comment 2 Jaroslav Škarvada 2022-01-26 09:31:35 UTC
It's blocking f36 mass rebuild of gnuradio now, bug 2045122.

Comment 3 Jaroslav Škarvada 2022-01-26 09:59:18 UTC
Possible dupe also: bug 2043040

Comment 4 Jakub Jelinek 2022-01-27 10:35:21 UTC
Please retry against gcc-12.0.1-0.3.fc36 and annobin-10.51-2.fc36 now in rawhide.

Comment 5 Jaroslav Škarvada 2022-01-28 14:02:05 UTC
(In reply to Jakub Jelinek from comment #4)
> Please retry against gcc-12.0.1-0.3.fc36 and annobin-10.51-2.fc36 now in
> rawhide.

Thanks, it works for me.


Note You need to log in before you can comment on or make changes to this bug.