Bug 805958 - "internal compiler error: Segmentation fault" error during xbmc compilation
Summary: "internal compiler error: Segmentation fault" error during xbmc compilation
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 17
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-22 14:45 UTC by Gökçen Eraslan
Modified: 2012-03-26 07:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-22 16:45:09 UTC
Type: ---


Attachments (Terms of Use)
Preprocessed source file (2.02 MB, text/plain)
2012-03-22 14:45 UTC, Gökçen Eraslan
no flags Details
Related ffmpeg header (137.22 KB, text/plain)
2012-03-22 14:52 UTC, Gökçen Eraslan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNU Compiler Collection 52671 0 P3 RESOLVED [4.7/4.8 Regression] ICE with misplaced attribute on enum 2020-08-18 17:41:53 UTC

Description Gökçen Eraslan 2012-03-22 14:45:44 UTC
Created attachment 572015 [details]
Preprocessed source file

Description of problem:

When I try to compile the latest snapshot of XBMC using this specfile[1], I got the following g++ error:

...
CPP     xbmc/cores/AudioRenderers/AudioRendererFactory.o
In file included from /home/gokcen/rpmbuild/BUILD/xbmc-xbmc-f38655f/lib/DllAvUtil.h:42:0,
                 from /home/gokcen/rpmbuild/BUILD/xbmc-xbmc-f38655f/lib/DllAvCore.h:28,
                 from /home/gokcen/rpmbuild/BUILD/xbmc-xbmc-f38655f/lib/DllAvCodec.h:27,
                 from /home/gokcen/rpmbuild/BUILD/xbmc-xbmc-f38655f/lib/DllAvFormat.h:27,
                 from EncoderFFmpeg.h:26,
                 from CDDARipper.cpp:34:
/usr/include/ffmpeg/libavcodec/avcodec.h:533:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
Preprocessed source stored into /tmp/cccKxqHv.out file, please attach this to your bugreport.
make[1]: *** [CDDARipper.o] Error 1
make: *** [xbmc/cdrip/cdrip.a] Error 2
make: *** Waiting for unfinished jobs....
CPP     xbmc/cores/AudioRenderers/ALSADirectSound.o
CPP     xbmc/cores/AudioRenderers/PulseAudioDirectSound.o
AR      xbmc/cores/AudioRenderers/audiorenderers.a
error: Bad exit status from /var/tmp/rpm-tmp.MjbBth (%build)

RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.MjbBth (%build)


I have tried with -O0 and default -O2 optimization flags, and both produced the same error.

Version-Release number of selected component (if applicable):
gcc-c++-4.7.0-0.20.fc17.x86_64
gcc-4.7.0-0.20.fc17.x86_64
ffmpeg-devel-0.8.9-1.fc17.x86_64

Steps to Reproduce:
1. Prepare a tarball of latest XBMC 11 Eden branch.
2. Update xbmc.spec accordingly.
3. Use rpmbuild -bb to compile spec file.


Additional info:

I'm using up-to-date Fedora 17 with updates-testing repository. Preprocessed source file is attached.

[1] http://download1.rpmfusion.org/free/fedora/development/source/SRPMS/repoview/xbmc.html

Comment 1 Gökçen Eraslan 2012-03-22 14:52:32 UTC
Created attachment 572016 [details]
Related ffmpeg header

referenced ffmpeg header is attached.

Comment 2 Jakub Jelinek 2012-03-22 16:45:09 UTC
__attribute__((deprecated)) on enum AVLPCType is misplaced, previously GCC would just warn that it ignores the attribute there and suggest where to put it, but 4.7/4.8 crashes on it.  Fixing that upstream now, but please report the misplaced attribute to whomever is responsible for that.

Comment 3 Gökçen Eraslan 2012-03-23 05:19:48 UTC
Thank you for quick response and gcc fix. I'll also inform ffmpeg package maintainer of rpmfusion repository.

Comment 4 Gökçen Eraslan 2012-03-26 07:15:05 UTC
Recently prepared gcc-4.7.0-1 package and gcc-4.7.0-20120322.tar.bz2 tarball does not include this fix, right?

Comment 5 Jakub Jelinek 2012-03-26 07:34:59 UTC
It doesn't, it will be only in subsequent updates.


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