From owner-freebsd-current@FreeBSD.ORG  Tue Mar  4 19:22:33 2014
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B42D6880;
 Tue,  4 Mar 2014 19:22:33 +0000 (UTC)
Received: from gw.catspoiler.org (gw.catspoiler.org [75.1.14.242])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 94637D03;
 Tue,  4 Mar 2014 19:22:33 +0000 (UTC)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.13.3/8.13.3) with ESMTP id s24JMH2k007015;
 Tue, 4 Mar 2014 11:22:21 -0800 (PST)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201403041922.s24JMH2k007015@gw.catspoiler.org>
Date: Tue, 4 Mar 2014 11:22:17 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: Status of llvm/clang 3.4?
To: emaste@FreeBSD.org
In-Reply-To: <CAPyFy2B=_1aCrrgdYAg+KF7OHfWoxLgAECZNR8gfi0rZg8B=7Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Cc: mueller6724@bellsouth.net, freebsd-current@FreeBSD.org,
 sgk@troutmask.apl.washington.edu
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Mar 2014 19:22:33 -0000

On  4 Mar, Ed Maste wrote:
> On 4 March 2014 12:22, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
>>
>> On Tue, Mar 04, 2014 at 12:17:18PM +0000, Thomas Mueller wrote:
>> > What is the current status of clang, regarding known bugs, on FreeBSD-current?
>> >
>> > There were reports of www/firefox failing to build because of bug in llvm.
>>
>> Still broken of i386.  Given the google results for "llvm ud2"
>> it is likely that clang will never be fixed.
> 
> Except in this case it's just a plain old Clang bug, not a general
> undefined behaviour issue.  The Clang PR is here:
> http://llvm.org/bugs/show_bug.cgi?id=19007
> 
> Dimitry has a patch to work around the issue in FreeBSD PR 187103:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=187103

In addtion to this firefox (and libxul - same fix applies) problem, I
also ran into problems with:
	multimedia/libxine		PR 187017	already fixed
	multimedia/gstreamer-ffmpeg	PR 187018	already fixed
	math/atlas			PR 186997	i386 only / patch in PR
	math/fftw*			PR 186998	i386 only / patch in PR
These are not clang bugs, but differences from gcc.

Also, not a clang bug, but caused by the lack of gcc in base:
	graphics/jogl			PR 187186	patch in PR

I also ran into a problem bulding math/py-numeric for i386 on a machine
with an Athlon 64 CPU, which causes -march=athlon64 to be set.  In this
case clang aborts.  I filed this bug bug report upstream:
<http://llvm.org/bugs/show_bug.cgi?id=19029>.

I ran into a few more broken ports, but the problems are not clang
related.