From owner-freebsd-toolchain@FreeBSD.ORG Mon Dec 27 22:10:50 2010 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id DF103106566B; Mon, 27 Dec 2010 22:10:50 +0000 (UTC) Date: Mon, 27 Dec 2010 22:10:50 +0000 From: Alexander Best To: Ade Lovett Message-ID: <20101227221050.GA54914@freebsd.org> References: <20101211114707.GA60390@freebsd.org> <4D051FD1.7070100@FreeBSD.org> <20101214204006.GA81772@freebsd.org> <4D0B8178.9010609@FreeBSD.org> <20101218154845.GA36640@freebsd.org> <20101218172130.GA49738@freebsd.org> <20101226210010.GA72359@freebsd.org> <44DC7721-D935-4957-AB1F-8D4776D3A2C2@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44DC7721-D935-4957-AB1F-8D4776D3A2C2@FreeBSD.org> Cc: freebsd-toolchain@freebsd.org Subject: Re: clang and -mfpmath=387 on ARCH=amd64 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Dec 2010 22:10:51 -0000 On Mon Dec 27 10, Ade Lovett wrote: > > On Dec 26, 2010, at 15:00 , Alexander Best wrote: > > it seems this issue is one of the cases where everybody is too afraid to make > > the actual commit. :( > > More likely, it's a case of let's get 7.4/8.2 out the door, with the usual rush of MFCs. > > I have a feeling that 9.0 (perhaps the entire 9.x tree) is going to be pretty brutal. Whether it's with gcc and clang side by side, or just clang. A change of this magnitude is going to _hurt_. if i understood the previous comments correctly this change will have *no* impact whatsoever appart from keeping stdout/stderr a bit cleaner. well...of course rushing changes is not a good idea but the opposide is just as bad. there are hundreds of very techie discussions where developers aggree on a certain item, but after the discussions ends nothing happens. e.g.: - switching the source for pciconf - mfc'ing the latest awk release to stable/7 - fixing some serious data corruption in the mailinglist archives - revising BDECFLAGS - ... plus numerous PRs which contain *correct* patches, now outdated due to their age. also this is very discouraging. a lot of people stop their community support, since their work (e.g. patches) dye of old age in some problem report. personally i write far less patches than i used too, simply because most of the time nobody will help you get the patches committed, even if they fix trivial spelling mistakes in manual pages. just my 0.02$. cheers. alex > > -aDe > -- a13x