X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Message-ID:	<480A123E.5B756F40@dessent.net>
Date:	Sat, 19 Apr 2008 08:39:42 -0700
From:	Brian Dessent <brian AT dessent DOT net>
X-Mailer:	Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version:	1.0
To:	Cory Cohen <cfcohen AT verizon DOT net>
CC:	cygwin AT cygwin DOT com
Subject:	Re: gcc version 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) Internal compiler error
References:	<480436C2 DOT 8020903 AT verizon DOT net> <480A1028 DOT 2040202 AT verizon DOT net>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Cory Cohen wrote:

> Several days ago I sent a bug report about an internal compiler error to
> the cygwin and gcc-bugs lists.  I've not heard back anything from either
> of the lists, and was wondering if there was something more that I
> needed to provide.  I realize there's no support contract here, and I'm
> not expecting that a solution be handed to me.  I'm happy to investigate
> further if someone will point me in the right direction.  But so far I
> think I've done exactly what was asked of me to report the report the
> problem...
> 
> Should I try to create a ticket in gcc bugzilla?  Has anyone been able
> to reproduce the problem?  Will cygwin or gcc track this problem?  Am I
> done, and I just need to wait patiently for someone to get to it?  I'm
> just wondering what to do now...

Reporting it to the Cygwin list is the correct place.  Don't bother
emailing gcc-bugs or any other gcc list, because a) gcc-bugs is mainly
just for bugzilla-generated traffic and isn't monitored for bugs not
reported through bugzilla, b) gcc 3.4 has not been closed and
unmaintained in years; you'd be directed to try 4.3 or 4.2, and c) our
gcc 3.4 is heavily patched anyway, part of the reason why we don't offer
4.x yet.

Brian

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

- Raw text -