Date: Wed, 29 Jan 2014 16:56:52 +0100 From: Michael Schmiedgen <schmiedgen@gmx.net> To: David Chisnall <theraven@FreeBSD.org> Cc: Dmitry Marakasov <amdmi3@amdmi3.ru>, FreeBSD Current <freebsd-current@FreeBSD.org> Subject: Re: [OT] ta-spring Message-ID: <52E924C4.5070002@gmx.net> In-Reply-To: <57D26185-3443-4EA4-822E-D6D50D23551F@FreeBSD.org> References: <20140129022743.GO52820@hades.panopticon> <7B2C5E6B-C845-4AFB-845F-AAF6F3C1F239@FreeBSD.org> <20140129144518.GR52820@hades.panopticon> <52E91955.9030406@gmx.net> <B93982A8-3151-4A30-89C9-74F83BEF9D71@FreeBSD.org> <52E92024.9010501@gmx.net> <57D26185-3443-4EA4-822E-D6D50D23551F@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 29.01.2014 16:42, David Chisnall wrote: > On 29 Jan 2014, at 15:37, Michael Schmiedgen <schmiedgen@gmx.net> wrote: >> On 29.01.2014 16:16, David Chisnall wrote: >>> On 29 Jan 2014, at 15:08, Michael Schmiedgen <schmiedgen@gmx.net> wrote: >> >> I thought OpenMP will be an integral part of LLVM/clang in near future, >> at least the front-end part? It seems there are plans to even integrate >> the runtime in the llvm project source tree: >> >> http://openmp.llvm.org/ >> >> Ok, so llvm/clang 3.4 obviously will not ship with OpenMP, but maybe >> later versions. > > Active development happens in Intel's tree, and is slowly being merged upstream. Eventually, Clang will have full OpenMP 4 support, but Intel's tree will have it first and there is likely to be a lag before it makes it into mainline clang. > > As such, it would make sense to have a port as a stop-gap until it is ready. > Ah, ok, that makes sense. Thanks for explanation. BTW very amusing *and* very informative bsdtalk/vBSDCon2013 talk a while ago, thanks for that! :) Cheers Michael
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52E924C4.5070002>