Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 17 Feb 2014 09:05:23 +0100
From:      "O. Hartmann" <ohartman@zedat.fu-berlin.de>
To:        Dimitry Andric <dim@FreeBSD.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: HEADS UP: Updated llvm/clang to 3.4 in r261991
Message-ID:  <20140217090523.51cf962e.ohartman@zedat.fu-berlin.de>
In-Reply-To: <6FA0FC8C-ABAA-433A-94AF-43AF84AD2AE4@FreeBSD.org>
References:  <6FA0FC8C-ABAA-433A-94AF-43AF84AD2AE4@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/4Dy1tgqgvuif8aW0zwHgzCX
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

On Sun, 16 Feb 2014 21:06:58 +0100
Dimitry Andric <dim@FreeBSD.org> wrote:

> Hi,
>=20
> I have just upgraded our copy of llvm/clang to 3.4 release, in r261991.
> This version supports all of the features in the current working draft
> of the upcoming C++ standard, provisionally named C++1y.
>=20
> The code generator's performance is greatly increased, and the loop
> auto-vectorizer is now enabled at -Os and -O2 in addition to -O3.  The
> PowerPC backend has made several major improvements to code generation
> quality and compile time, and the X86, SPARC, ARM32, Aarch64 and SystemZ
> backends have all seen major feature work.
>=20
> Release notes for llvm and clang can be found here:
> <http://llvm.org/releases/3.4/docs/ReleaseNotes.html>;
> <http://llvm.org/releases/3.4/tools/clang/docs/ReleaseNotes.html>;
>=20
> Note that building lldb (using WITH_LLDB) will not work at this point,
> since our lldb snapshot was locally modified to be able to work with the
> old llvm 3.3 API.  Ed Maste will most likely fix this very soon (and
> maybe import a new snapshot, I hope :-).
>=20
> Another important aspect for end-users and ports maintainers is the new
> compiler flag handling in clang 3.4.  It has become more strict, in the
> sense that it will now error out on flags it does not recognize, in
> particular most gcc-specific optimization fine-tuning flags.
>=20
> Some ports which blindly use such gcc-specific flags will therefore be
> broken, but these are usually very easy to fix.  During the exp-run
> which was done with this new version of clang, several ports with the
> highest number of dependent ports (open-motif, libtheora, boost-libs,
> etc) have already been handled, but more work still needs to be done.
>=20
> Last but not least, I hope we can now start using clang for more of our
> existing architectures, like powerpc, mips, and possibly even new ones
> like arm64.  Enjoy!
>=20
> -Dimitry
>=20

Dimitry,

I want to say thank you and the Mannschaft for the work you've done.=20

Regards,
Oliver

--Sig_/4Dy1tgqgvuif8aW0zwHgzCX
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (FreeBSD)

iQEcBAEBAgAGBQJTAcLDAAoJEOgBcD7A/5N8cV0H/2pKzgNuMEYa2YmXs4d4xZI4
dgtzcIEi7Nto6CPv9EKFnURIWO0vCvdYfvMz4UVu2i27bNQwJa0TUMhUVoKXb4HK
1JWibiKXatPhS05vyEVxwKL7IPNx+h80BHEr8h7sqgU7mmJ0A9aDYRMrtnpNBoWi
GwzulNI+vj3pp3v1G4TXf/8nAzvATHH81/MGcCbI0LO8TYgvr3ox15A5Y2nXzym/
KSYUk1ldOOYof2AIvDp6ou07n740mCxlLp/vLuS1MeWLvl2wPJ99LLZCVSnuczx8
7azzCPNQay2KSU870ye+Y6l0bxCb8pYQCymkCU/rquE2vzuJCSe1TmzwYOdUiKE=
=oght
-----END PGP SIGNATURE-----

--Sig_/4Dy1tgqgvuif8aW0zwHgzCX--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140217090523.51cf962e.ohartman>