Bug 1317069 - compiler segfualt
Summary: compiler segfualt
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 22
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-11 20:58 UTC by Steven Brandt
Modified: 2016-07-19 19:24 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-19 19:24:58 UTC
Type: Bug

Attachments (Terms of Use)
compiler segfaults for gnu-tm and c++11 (929.77 KB, text/x-csrc)
2016-03-11 20:58 UTC, Steven Brandt 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.