similar to: Running the compiler-rt builtins unit tests

W dniu wto, 16.10.2018 o godzinie 18∶25 +0100, użytkownik Rowland Penny via samba napisał: > On Tue, 16 Oct 2018 18:47:30 +0200 > "Zuzanna K. Filutowska via samba" <samba at lists.samba.org> wrote: > > > Dear All, > > > > I have a setup with samba acting as active directory domain > > controller, DNS updates are done via bind DLZ. I have

On Wed, Aug 30, 2017 at 2:14 PM, Michał Górny <mgorny at gentoo.org> wrote: > W dniu wto, 29.08.2017 o godzinie 16∶52 -0700, użytkownik Hans Wennborg > via llvm-dev napisał: >> Hello testers, >> >> 5.0.0-rc4 was just tagged. >> >> There were very few changes after rc3, and if nothing unexpected comes >> up, this is what the final release will look

W dniu wto, 16.10.2018 o godzinie 18∶52 +0100, użytkownik Rowland Penny via samba napisał: > On Tue, 16 Oct 2018 19:37:21 +0200 > "Zuzanna K. Filutowska via samba" <samba at lists.samba.org> wrote: > > > W dniu wto, 16.10.2018 o godzinie 18∶25 +0100, użytkownik Rowland > > Penny via samba napisał: > > > On Tue, 16 Oct 2018 18:47:30 +0200 > >

Hello testers, 5.0.0-rc4 was just tagged. There were very few changes after rc3, and if nothing unexpected comes up, this is what the final release will look like. Please test and let me know if there are any issues. Cheers, Hans

I am attempting to port an operating system project to use Clang/LLVM instead of GCC, but I'm having issues with Compiler-RT. Right now, the OS is being cross-compiled on an x86_64 host targeting ARMv7a. I built the LLVM toolchain according to the instructions, though I limited the supported targets to arm, x86, and x86_64 to reduce compilation time. I'm finding that compilation proceeds

Hi, Short version: Is it possible to enable *all* builtins architectures? How? Longer explanation: I don't quite understand how compiler-rt targets are decided to be built while invoking cmake from the LLVM tree. I tend to believe that builtins and sanitizers (the two big parts in compiler-rt) are quite different monsters, but however they share the same build decisions and (if I'm not

> On Nov 2, 2015, at 11:41 AM, Vasileios Kalintiris <Vasileios.Kalintiris at imgtec.com> wrote: > >> The problem comes when bootstrapping a cross-compiler toolchain. In order to >> have a cross-compiling toolchain that can build a “hello world” application you >> need four basic components: >> >> (1) clang >> (2) ld >> (3) libclang_rt

Is there any specific reason why the clang_rt.builtins-${arch} library is disabled for windows builds? if (NOT WIN32) foreach(arch x86_64 i386 arm) if(CAN_TARGET_${arch}) set_source_files_properties(${${arch}_SOURCES} PROPERTIES LANGUAGE C) add_compiler_rt_runtime(clang_rt.builtins-${arch} ${arch} STATIC SOURCES ${${arch}_SOURCES} CFLAGS

On 8 July 2014 19:47, Alexey Samsonov <vonosmas at gmail.com> wrote: > compiler-rt/lib/builtins/arm/*.S files are listed in arm_SOURCES variable, > and therefore should make it into the builtins static library on ARM. Don't > they? I assume so... But I'm not an expert in CMake.

Dear All, I have a setup with samba acting as active directory domain controller, DNS updates are done via bind DLZ. I have recompiled it to allow spnego. DHCP server is external, no changes in it are possible. Domain members try to register in the DNS, KDC is aware of them, however no DNS entries for them are created and BIND returns errors. Any hints are welcome since I really need it working.

I believe the C source files in builtins directory are generic enough. Why not build a clang_rt.builtins-aarch64 library? --Sumanth G -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140708/969ee15b/attachment.html>

I noticed the compiler-rt/lib/builtins/CmakeLists.txt is not including the .S files in building clang_rt.builtins-arm.a We need to tell the CMake build system that the .S files are also the source files. Is there any intention behind leaving the .S files not to compile? If not, let me know and I will push a patch. --Sumanth G -------------- next part -------------- An HTML attachment

> On Nov 2, 2015, at 10:10 AM, Anton Korobeynikov <anton at korobeynikov.info> wrote: > >> Today building this toolchain with CMake is impossible because you cannot configure the cross-compiled builtins. The failure is a result of CMake’s try_compile function always testing a full compile then link operation. When bootstrapping a cross-compiler this will always fail because

In the effort to flesh out the CMake build system a problematic issue has come up, and I’d like some feedback on how to best handle it. For reference this issue has been reported by a few users, one proposed patches that don’t really address the underlying problem here: http://reviews.llvm.org/D13131 The problem comes when bootstrapping a cross-compiler toolchain. In order to have a

Hi, compiler-rt builtins currently doesn't build on MSVC 2019, I the problem is that compiler-rt\lib\builtins\int_math.h includes the header ymath.h. according to eg. https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/finite-finitef?view=vs-2019 the header to include is float.h also the ymath.h file contains the comment /* ymath.h internal header */ so probably shall not be

On Tue, Jul 8, 2014 at 2:44 PM, sgundapa <sgundapa at codeaurora.org> wrote: > No. CMake has different way of treating the .S files > Refer to http://www.cmake.org/Wiki/CMake/Assembler > > I have a patch which will make CMake treat the .S files as source files. > Let me guess, you should just call set_source_file_properties(<arm .S files> PROPERTIES LANGUAGE C)? >

On Tue, Nov 3, 2015 at 6:33 AM, Martell Malone <martellmalone at gmail.com> wrote: > Just as a point for building the builtins shouldn't we just need llvm-ar ? Thanks for pointing this out and I hope llvm-ar is up to the task. Even if targets must still port binutils, each step toward LLVM self-reliance is a step in the right direction. Without getting too far ahead of ourselves,

Sure, we can build libclang_rt.builtins-aarch64.a, if there are users for it and, ideally, someone able to setup a buildbot and keep it in a working state. On Tue, Jul 8, 2014 at 11:32 AM, sgundapa <sgundapa at codeaurora.org> wrote: > I believe the C source files in builtins directory are generic enough. > > Why not build a clang_rt.builtins-aarch64 library? > > > >

> On Dec 18, 2016, at 3:48 AM, Dmitry Golovin <dima at golovin.in> wrote: > > > > 16.12.2016, 18:23, "Vedant Kumar" <vsk at apple.com>: >>> On Dec 16, 2016, at 7:06 AM, Dmitry Golovin via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> I want to build LLVM-based toolchain with Musl, I have LLVM sources with clang and

Hi @ll, compiler-rt implements (for example) the MSVC (really Windows) specific routines compiler-rt/lib/builtins/i386/chkstk.S and compiler-rt/lib/builtins/x86_64/chkstk.S as __chkstk_ms() See <http://msdn.microsoft.com/en-us/library/ms648426.aspx> Is there any special reason why compiler-rt doesn't implement other MSVC specific functions (alias builtins or "compiler