Bug 1317069

Summary: compiler segfualt
Product: [Fedora] Fedora Reporter: Steven Brandt <sbrandt>
Component: gccAssignee: Jakub Jelinek <jakub>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 22CC: davejohansen, jakub, jwakely, law, mpolacek, rth
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 19:24:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
compiler segfaults for gnu-tm and c++11 none

Description Steven Brandt 2016-03-11 20:58:13 UTC
Created attachment 1135401 [details]
compiler segfaults for gnu-tm and c++11

Description of problem:

g++ -fgnu-tm -std=c++11 file.cpp

on the attached file causes a segfualt.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. cp cc8tvLKH.out file.cpp
2. g++ -fgnu-tm -std=c++11 file.cpp
3.

Actual results:
segfault

Expected results:
a compiled file

Additional info:

Comment 1 Jakub Jelinek 2016-03-17 15:29:03 UTC
This got fixed on the trunk with PR67811.  No idea whether it is backportable, or whether we should just close as fixed for Fedora 24, CCing patch author.

Comment 3 Fedora End Of Life 2016-07-19 19:24:58 UTC
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.