Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 12 Sep 2012 10:50:15 -1000
From:      Doug Barton <dougb@dougbarton.us>
To:        David Chisnall <theraven@theravensnest.org>
Cc:        toolchain@freebsd.org, Roman Divacky <rdivacky@freebsd.org>, Dimitry Andric <dim@freebsd.org>, current@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu>
Subject:   Re: Clang as default compiler November 4th
Message-ID:  <5050F587.6010105@dougbarton.us>
In-Reply-To: <7778270C-218B-4F23-9941-D6DBED8E054D@theravensnest.org>
References:  <20120910211207.GC64920@lor.one-eyed-alien.net> <20120911104518.GF37286@deviant.kiev.zoral.com.ua> <20120911120649.GA52235@freebsd.org> <20120911132410.GA87126@troutmask.apl.washington.edu> <504F4645.4070900@FreeBSD.org> <20120911150356.GA87526@troutmask.apl.washington.edu> <5050513C.7040100@dougbarton.us> <7778270C-218B-4F23-9941-D6DBED8E054D@theravensnest.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 9/12/2012 1:49 AM, David Chisnall wrote:
> On 12 Sep 2012, at 10:09, Doug Barton wrote:
> 
>> Also, users who actually are helping with testing clang for ports
>> continue to report runtime problems, even with things that build fine.
> 
> I hope that you are encouraging maintainers of ports that don't work as expected with clang to submit bug reports upstream.  We can't fix bugs if we aren't made aware of them.

I personally am not directly involved in this effort (other than for my
own ports), but from what I've seen the classical emphasis on pushing
bug reports upstream has been applied in this area as well.

hth,

Doug



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5050F587.6010105>