From owner-freebsd-alpha  Tue Mar 20  7:27:15 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id C2B9437B71C
	for <freebsd-alpha@FreeBSD.ORG>; Tue, 20 Mar 2001 07:27:12 -0800 (PST)
	(envelope-from gallatin@cs.duke.edu)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id KAA12693;
	Tue, 20 Mar 2001 10:23:04 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f2KFMYh92566;
	Tue, 20 Mar 2001 10:22:34 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15031.30138.214213.123377@grasshopper.cs.duke.edu>
Date: Tue, 20 Mar 2001 10:22:34 -0500 (EST)
To: naddy@mips.inka.de (Christian Weisgerber)
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: How serious are we about ccc?
In-Reply-To: <99656d$hgs$1@kemoauc.mips.inka.de>
References: <99656d$hgs$1@kemoauc.mips.inka.de>
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Christian Weisgerber writes:
 > Do we consider ccc (ports/lang/compaq-cc) just a curiosity and
 > squarely put the blame on ccc if something doesn't build with it,
 > or do we want ccc do have a modicum of usefulness?

No.  Yes(*) Yes.

(*) But it might be fixable, via comp.config.

 > Lest this be misunderstood, I'm merely asking an honest question.
 > I recently built the mawk port with ccc, which works.  Today I've
 > tried Ogg Vorbis.  Libtool doesn't handle building shared libraries
 > with ccc (which I would assume to be a configuration issue) and
 > the compiler dies on some of our system header files, which I
 > haven't examined yet.  Is there any worth in investigating these
 > problems?

Yes, very much so.  The gnu compiler is terrible on the alpha
platform.  Not only does it produce slow code, it produces broken code
and/or crashes at even modest optimization levels.

Wrt dying on the system header files,  I assume you are aware of how
to setup the comp.config so that it searches ccc specific versions of our
header files prior to looking in /usr/include?  Check out
/usr/lib/compaq/ccc-($version)/alpha-linux/bin/comp.config

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message