On 05/11/16 17:57, Pauli wrote:
> On Wed, 5 Oct 2016 23:33:49 +1300, Bruce Hoult wrote:
>> On Wed, Oct 5, 2016 at 7:46 AM, Tim Northover via llvm-dev <
>> llvm-...@lists.llvm.org> wrote:
>>
>>> Hi Emilio,
>>>
>>> On 4 October 2016 at 11:14, Emilio Pozuelo Monfort via llvm-dev
>>> wrote:
In fi
Le 05/11/2016 à 17:57, Pauli a écrit :
On Wed, 5 Oct 2016 23:33:49 +1300, Bruce Hoult wrote:
On Wed, Oct 5, 2016 at 7:46 AM, Tim Northover via llvm-dev <
llvm-...@lists.llvm.org> wrote:
Hi Emilio,
On 4 October 2016 at 11:14, Emilio Pozuelo Monfort via llvm-dev
wrote:
In file included from /
On Wed, 5 Oct 2016 23:33:49 +1300, Bruce Hoult wrote:
> On Wed, Oct 5, 2016 at 7:46 AM, Tim Northover via llvm-dev <
> llvm-...@lists.llvm.org> wrote:
>
> > Hi Emilio,
> >
> > On 4 October 2016 at 11:14, Emilio Pozuelo Monfort via llvm-dev
> > wrote:
> > > In file included from /«PKGBUILDDIR»/lib/
On Wed, Oct 5, 2016 at 7:46 AM, Tim Northover via llvm-dev <
llvm-...@lists.llvm.org> wrote:
> Hi Emilio,
>
> On 4 October 2016 at 11:14, Emilio Pozuelo Monfort via llvm-dev
> wrote:
> > In file included from /«PKGBUILDDIR»/lib/Support/ThreadPool.cpp:14:0:
> > /«PKGBUILDDIR»/include/llvm/Support/
Hi Tim,
On 04/10/16 20:46, Tim Northover wrote:
> Hi Emilio,
>
> On 4 October 2016 at 11:14, Emilio Pozuelo Monfort via llvm-dev
> wrote:
>> In file included from /«PKGBUILDDIR»/lib/Support/ThreadPool.cpp:14:0:
>> /«PKGBUILDDIR»/include/llvm/Support/ThreadPool.h: In member function
>> 'std::shar
Hi Emilio,
On 4 October 2016 at 11:14, Emilio Pozuelo Monfort via llvm-dev
wrote:
> In file included from /«PKGBUILDDIR»/lib/Support/ThreadPool.cpp:14:0:
> /«PKGBUILDDIR»/include/llvm/Support/ThreadPool.h: In member function
> 'std::shared_future llvm::ThreadPool::async(Function&&, Args&& ...)':
Hi,
peter green wrote:
> On 18/05/16 04:50, Tim Northover wrote:
> If you don't need/want the various Sanitizer runtimes (e.g. you don't
> support sanitizers or already have versions provided with GCC) then
> it's as easy as not downloading compiler-rt or removing it from the
> projects/ directory
On 18/05/16 04:50, Tim Northover wrote:
If you don't need/want the various Sanitizer runtimes (e.g. you don't
support sanitizers or already have versions provided with GCC) then
it's as easy as not downloading compiler-rt or removing it from the
projects/ directory before running CMake. The build
On 17 May 2016 at 15:15, peter green via llvm-dev
wrote:
> Can you tell me how I would go about telling the cmake buildsystem (which is
> what the Debian packaging currently seems to use) that I want it to build
> without compiler-rt?
If you don't need/want the various Sanitizer runtimes (e.g. yo
On 17/05/16 22:38, Tim Northover wrote:
Compiler-rt is the equivalent of libgcc, and Clang can use the
existing host's libgcc quite happily so it's really not that important
unless you're trying to build a GNU-free environment for whatever
reason.
Thanks
Can you tell me how I would go about
> Can you clarify what exactly compiler-rt is and how important it is to the
> stack as a whole. It seems that llvm-toolchain-3.7 built successfully on
> raspbian without building compiler-rt while llvm-toolchain-3.8 built an
> armv7 compiler-rt (and hence got blocked from entering the raspbian rep
On 17/05/16 18:07, Tim Northover wrote:
Yes, it looks like we'd need to conditionally compile these functions
in ARM mode and use the v6 barrier instead of dmb ("mcr p15, #0, r0,
c7, c10, #5" I believe) to support the ARM1176JZF-S in RPi. You'd
probably also want the build system to use an explic
On 5/17/16 11:07 AM, Tim Northover via llvm-dev wrote:
Hi Peter,
On 16 May 2016 at 22:25, peter green via llvm-dev
wrote:
I traced this back to code in compiler-rt/lib/builtins/arm/sync-ops.h . The
comments talk about both arm mode and thumb2 mode code but I only actually
see thumb2 code in
Hi Peter,
On 16 May 2016 at 22:25, peter green via llvm-dev
wrote:
> I traced this back to code in compiler-rt/lib/builtins/arm/sync-ops.h . The
> comments talk about both arm mode and thumb2 mode code but I only actually
> see thumb2 code in the file. I'm kinda stuck here.
Yes, it looks like we
llvm-toolchain-3.8 seems to have problems on debian armel and raspbian.
On raspbian it builds but our armv7 contamination checker blocked it
from entering the repo. Further investigation showed that "compiler-rt"
was being built with -march=armv7 . I was able to remove the -march with
some bui
15 matches
Mail list logo