Date: Thu, 15 Oct 2015 14:00:04 +0200 From: "O. Hartmann" <ohartman@zedat.fu-berlin.de> To: Dimitry Andric <dim@FreeBSD.org> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: Fixed with r289221 (was: Re: CURRENT: build failure with clang 3.7.0) Message-ID: <20151015140004.0ff72dfb@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: <578D8BA0-F9B6-4C97-BEBF-C197F4CBC57D@FreeBSD.org> References: <20151007093727.0db8e2e6@freyja.zeit4.iv.bundesimmobilien.de> <EB5AD370-5FFF-4C90-8510-14DB3EFED961@FreeBSD.org> <20151007133323.364655dd@freyja.zeit4.iv.bundesimmobilien.de> <2B9A426D-12FE-4D70-9182-7F84408A6001@FreeBSD.org> <20151010181242.5d8e2da1.ohartman@zedat.fu-berlin.de> <EBA4D069-8223-47E7-B750-0B8E568F279E@FreeBSD.org> <578D8BA0-F9B6-4C97-BEBF-C197F4CBC57D@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 13 Oct 2015 18:30:08 +0200 Dimitry Andric <dim@FreeBSD.org> wrote: > On 10 Oct 2015, at 19:39, Dimitry Andric <dim@FreeBSD.org> wrote: > > > > On 10 Oct 2015, at 18:12, O. Hartmann <ohartman@zedat.fu-berlin.de> wrote: > > ... > >> Is there any chance that the failure of clang 3.7.0 with some AVX-equipted > >> Intel processors gets fixed soon? > > > > I reported the bug upstream, did number of bisections to drill down to > > the root cause (hopefully), and found an LLVM committer who has made a > > "quick hack" fix. This fix needs further review and test cases, though, > > before it is sane enough to commit upstream, and to import into our > > tree. This work will probably be done after the weekend. > > I committed the upstream fix in r289221. You should now be able to use > CPUTYPE safely again. Let me know if anything still breaks. :) > > -Dimitry > Everything is well and shiny again. Thank you very much. Oliver
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151015140004.0ff72dfb>