From owner-freebsd-ports@FreeBSD.ORG Thu Nov 24 23:23:21 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 86D7E16A41F for ; Thu, 24 Nov 2005 23:23:21 +0000 (GMT) (envelope-from tridge@samba.org) Received: from lists.samba.org (dp.samba.org [66.70.73.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A75043D5F for ; Thu, 24 Nov 2005 23:23:03 +0000 (GMT) (envelope-from tridge@samba.org) Received: by lists.samba.org (Postfix, from userid 603) id 78594162C26; Thu, 24 Nov 2005 23:23:03 +0000 (GMT) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <17286.19420.469358.628281@samba.org> Date: Fri, 25 Nov 2005 10:25:16 +1100 To: Jens Schweikhardt In-Reply-To: <20051124230220.GB1923@schweikhardt.net> References: <200511210625.16973.ringworm01@gmail.com> <20051124182645.GA1923@schweikhardt.net> <17286.14954.340289.972852@samba.org> <20051124230220.GB1923@schweikhardt.net> X-Mailer: VM 7.19 under Emacs 21.4.1 From: tridge@samba.org Cc: "Andrew P." , freebsd-ports@freebsd.org, sobomax@portaone.com Subject: Re: FreeBSD ccache port is wonderfiul! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: tridge@samba.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Nov 2005 23:23:21 -0000 Jens, > I'm not sure I understand what you mean by "not use compiler > bootstrapping". It's a non-optional part of the FreeBSD build and I like > to start from scratch. A new world *must* build, install, and use a > temporary environment. My point is that if you are using tricks to defeat the compiler has changed test in ccache, then you are not really using the temporary environment. You are using it for some things, but for some parts of the build you are using an earlier environment. That's why I wondered if there should be a varient of buildworld that uses an existing compiler, rather than using the one built in the temporary environment. It just makes it a little clearer what risks are being taken. I've never actually built freebsd though, so I might be talking through my hat, and feel free to ignore me :-) > Here it's > schweikh@hal9000:~ $ ll /usr/local/libexec/ccache/bin > total 486 > -r-xr-xr-x 1 root wheel 77296 Nov 9 22:35 c++ > -r-xr-xr-x 1 root wheel 4080 Nov 9 22:35 c89 > -r-xr-xr-x 1 root wheel 4380 Nov 9 22:35 c99 > -r-xr-xr-x 1 root wheel 164956 Nov 9 22:35 cc > -r-xr-xr-x 1 root wheel 77296 Nov 13 16:27 g++ > -r-xr-xr-x 1 root wheel 164956 Nov 13 16:27 gcc that's quite small, and I suspect that the speed of CCACHE_HASH_COMPILER will be good. > Will do, but I'm moving and it may take until January for a definitive > go/no go. no worries. I've put the change in ccache anyway, I'm just curious to know if this is a workable compromise for freebsd. > Yes, I always wondered about that, too. cc1 is the actual binary > responsible for code generation, maybe even the assembler must be > considered. Looking at the compiler driver may give false positives, if > only cc1 or as changes (unlikely, but maybe not just of academic > interest). I've heard of that problem with some gcc developers, who manually install just the 2nd stage or the assembler when they are trying out new techniques. I have thought about having a CCACHE_HASH_LIST option that would take a list of files, but I haven't put it in as I suspect the number of people that need it would be very small, and those probably won't trust a compiler cache anyway :-) > That's great news, thanks! Any plans for a 2.5 release? We are probably about due for one, though the changes since 2.4 are quite small. I'll have a look in my patch queue :-) Cheers, Tridge