From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-105537-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 8883 invoked by alias); 22 Nov 2004 02:29:08 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 8837 invoked from network); 22 Nov 2004 02:29:04 -0000
Received: from unknown (HELO mailhub129.itcs.purdue.edu) (128.210.5.129)
  by sourceware.org with SMTP; 22 Nov 2004 02:29:04 -0000
Received: from [128.210.3.29] (descartes.math.purdue.edu [128.210.3.29])
	by mailhub129.itcs.purdue.edu (8.12.10/8.12.10/scan-smtp) with ESMTP id iAM2SxmH009404;
	Sun, 21 Nov 2004 21:28:59 -0500
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <446EB888-3C2E-11D9-A429-000A958F150A@math.purdue.edu>
Content-Transfer-Encoding: 7bit
Cc: Bradley Lucier <lucier@math.purdue.edu>, gcc@gcc.gnu.org
From: Bradley Lucier <lucier@math.purdue.edu>
Subject: Re: Is it time to start using 4.0?
Date: Mon, 22 Nov 2004 04:20:00 -0000
To: mrs@apple.com
X-Virus-Scanned: by amavisd-new
X-SW-Source: 2004-11/txt/msg00730.txt.bz2

Re:

> We expect that the quality of the compiler is close to release 
> quality, generally, I'd say that we like to keep it near release 
> quality, though, bear in mind, if you get unlucky, you may find some 
> temporal instabilities.

Well, I must be really unlucky, since 4.0 has never correctly compiled 
C code generated by the Gambit-C 4.0 beta Scheme->C compiler.  It's 
true that about once a month somebody fixes something that gets rid of 
another code generation problem, but I'll consider 4.0 "close to 
release quality" when I can start testing code generation quality and 
compiler run times rather than code generation correctness.

Brad

PS:  If anyone can tell me which version, if any, of gdb on either x86 
linux, sparc solaris 9, or MacOS 10.3.6, can give me accurate debug 
information for code compiled by 4.0 with options

FLAGS_OBJ = -O1 -fno-math-errno -fschedule-insns2 -fno-trapping-math 
-fno-strict-aliasing -fomit-frame-pointer -fPIC

I would really appreciate it.