DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:to:from:subject:message-id:date:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=wok
	Z4Kt+S/vew0RQcGcgQkf52qssq6zto2COiwL5yDDsk4IBpIrs8EhNdpBV4nHlZyc
	W+/dVAv72p39WAET8qCaiDv6gPR9xy4X6US/ooGT9HPUdKnYT7JHk2EsaxScgIRy
	U2wdAIOvugy06cOuF8P0QDG0hktMgq6u78dJW4+Q=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: jeff <jeff AT jeffunit DOT com>
Subject: Re: I sent in a bug report and never heard anything back
Message-ID: <e4f9f62e-ec33-0c68-42b1-d157262d4590@jeffunit.com>
Date: Fri, 26 Aug 2016 21:44:32 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

Hans-Bernhard Bröker <HBBroeker at t-online dot de> wrote:

Not necessarily. Traditionally the typical reason for GCC internal
compiler errors, particularly if they occur with old source on very new
machines, has been faulty hardware.


My reply:

While it is always possible that there is a hardware issue, I suspect
that is not likely in this case.
The specific notebook dual boots to mageia 5 linux, and using gcc 4.9.2
the code in question compiles and runs without issue. So I suspect it is
more likely a compiler bug.

I can't imagine that I am the only person using cygwin with this issue,
so it might be good for the cygwin people to address it.

Since I sent the bug report in Aug 1, and I have gotten no useful
response from cygwin, I will be reporting the issue directly to the gcc
folks.

jeff

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple