delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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 |
Message-ID: | <30C9E24891FFD411B68A009027724CB7443403@eg-002-015.eglin.af.mil> |
From: | Keen Wayne A Contr AFRL/MNGG <keenwa AT eglin DOT af DOT mil> |
To: | "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com> |
Subject: | gcc 3.1 |
Date: | Fri, 31 May 2002 11:13:11 -0500 |
Note-from-DJ: | This may be spam |
There have been some posts regarding this on the gcc page in the last week, on in part read: "gcj on cygwin is absolutely bleeding edge. Hans Boehm tells me there are garbage collector patches still to be applied, and it may crash randomly in unusual ways. Almost certainly other runtime problems as well. " Check out the gcc archives. I wanted to send a link, but the SPAM filter had a problem with that, I think. I have reached far beyond what I really know on the topic. :-) Wayne Keen -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |