Bug 910153 - qemu-1.3.0/cpu-exec.c:671:1: internal compiler error: in push_reload, at reload.c:1014
Summary: qemu-1.3.0/cpu-exec.c:671:1: internal compiler error: in push_reload, at relo...
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: ARMTracker
TreeView+ depends on / blocked
 
Reported: 2013-02-11 22:04 UTC by Peter Robinson
Modified: 2013-02-15 09:06 UTC (History)
3 users (show)

Fixed In Version: gcc-4.8.0-0.12.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-15 09:06:04 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Preprocessed cpu-exec.c (542.81 KB, text/plain)
2013-02-12 02:10 UTC, Brendan Conoboy
no flags Details

Description Peter Robinson 2013-02-11 22:04:25 UTC
Seeing the following error on gcc 4.8 on ARMv8.

qemu-1.3.0/cpu-exec.c:671:1: internal compiler error: in push_reload, at reload.c:1014

http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1434338

Package is qemu-1.3.0-9.fc19

gcc is gcc-4.8.0-0.9.fc19

Let me know if you need anything further.

Comment 1 Peter Robinson 2013-02-11 22:13:42 UTC
seeing the same issue with ntfs-3g-2013.1.13-3.fc19

http://arm.koji.fedoraproject.org/koji/taskinfo?taskID=1434867

Pushing a gcc-4.8.0-0.11.fc19 in case it's fixed in a later build

Comment 2 Brendan Conoboy 2013-02-11 23:21:29 UTC
Is this the same as http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56184 ?

Comment 3 Brendan Conoboy 2013-02-12 00:05:31 UTC
Note that Peter said "ARMv8" but clearly meant "armv7"

Comment 4 Brendan Conoboy 2013-02-12 02:10:23 UTC
Created attachment 696338 [details]
Preprocessed cpu-exec.c

Comment 5 Peter Robinson 2013-02-13 19:01:03 UTC
Can we get the upstream bug fix pulled from the aforementioned bug? We need it for ARM mass rebuild

Comment 6 Peter Robinson 2013-02-15 09:06:04 UTC
Confirmed fixed in gcc-4.8.0-0.12.fc19


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