From owner-freebsd-stable@FreeBSD.ORG Tue May 29 16:59:26 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3142B106566B for ; Tue, 29 May 2012 16:59:26 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id DF0118FC0C for ; Tue, 29 May 2012 16:59:25 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:1966:3960:5466:61dc] (unknown [IPv6:2001:7b8:3a7:0:1966:3960:5466:61dc]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id D352B5C59; Tue, 29 May 2012 18:59:18 +0200 (CEST) Message-ID: <4FC50065.3030201@andric.com> Date: Tue, 29 May 2012 18:59:17 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120522 Thunderbird/13.0 MIME-Version: 1.0 To: David Wolfskill , James , FreeBSD Stable References: <20120529162701.GZ1509@albert.catwhisker.org> In-Reply-To: <20120529162701.GZ1509@albert.catwhisker.org> X-Enigmail-Version: 1.5a1pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: Possible Clang regression - object files are always mode 0600 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 May 2012 16:59:26 -0000 On 2012-05-29 18:27, David Wolfskill wrote: > On Tue, May 29, 2012 at 01:39:19AM -0500, James wrote: >> Hi all. I've come across a possible Clang regression that recently >> crept into stable/9. I'd like to check to see whether it's a true bug >> or if I jacked something up. It appears all object files are created >> with mode 0600 rather than honoring umask. Just so you know, this is indeed a regression that has crept into clang, and even into the 3.1 release. :( I'm working on fixing it in head, then I will merge the fix to stable/9 in a few days.