search for: libcompil

...se, and do let me know of any issues, >> questions, etc. >> >> The tracking bug for release blockers is PR24126. > > Is it OK to do an autoconf build? The CMake build tries to build various components which do not yet work on FreeBSD, e.g. libcxxabi does not compile at all, libcompiler-rt has a bunch of test failures, etc. Alternatively, can I disable these components in the CMake build locally? Yes, go ahead and use the autoconf build. Can you send a patch to test-release.sh that makes this default for FreeBSD? It's already the default for Darwin. Thanks, Hans

...place libgcc yet? I know Apple is using > compiler-rt built runtime libs. How did they link? What compiler are you using? compiler-rt was designed to implement the support functions needed for clang. If you are compiling with gcc, then, yes you might find it relies on support functions not in libcompiler-rt.a. -Nick

...t;>>> questions, etc. >>>> >>>> The tracking bug for release blockers is PR24126. >>> >>> Is it OK to do an autoconf build? The CMake build tries to build various components which do not yet work on FreeBSD, e.g. libcxxabi does not compile at all, libcompiler-rt has a bunch of test failures, etc. Alternatively, can I disable these components in the CMake build locally? >> >> Yes, go ahead and use the autoconf build. >> >> Can you send a patch to test-release.sh that makes this default for >> FreeBSD? It's already the...

...w Apple is using >> compiler-rt built runtime libs. How did they link? > > What compiler are you using? compiler-rt was designed to implement the > support functions needed for clang. If you are compiling with gcc, then, > yes you might find it relies on support functions not in libcompiler-rt.a. > > -Nick > >

Hi, I'm trying to link my objs with compiler-rt built runtime lib for arm. According to the compiler-rt doc, it should be able to replace libgcc. However, if I replace "-lgcc" with "compiler-rt.a" for a static linking, gcc linker complains about undefined functions. Using "nm -g", I compared the functions in libgcc and compiler-rt.full-arm.a and found there are

...ing make build system > seems more feasible. I've combined the compiler_rt/make/platform/ > clang_linux.mk and the compiler_rt/make/platform/clang_macho_embedded.mk. > So far it could cross-compile all of the files in > "compiler-rt/lib/builtins/" (*.c files). However, the libcompiler_rt.a > still missing functions such as "__aeabi_memset", "__aeabi_memcpy". These > functions were in "compiler_rt/lib/biltins/arm/" (*.S) files. They are not > included in any of the *.mk files. Do you have any idea on how to add these > assembly sources...

Hi, I'm using compiler-rt to build the library to replace libgcc. How can I disable -lgcc being added and passed to the linker? When I use: "clang -ccc-gcc-name arm-cross-g++ hello.c -Lmypath -lmylib -v" -lgcc is always added: "...gcc/arm-none-linux-gnueabi/4.6.1/collect2 ... /tmp/hello-Pj9QxO.o -lgcc ..." How can I disable or override libgcc from the command line?

...gt;>>>>> >>>>>> The tracking bug for release blockers is PR24126. >>>>> >>>>> Is it OK to do an autoconf build? The CMake build tries to build various components which do not yet work on FreeBSD, e.g. libcxxabi does not compile at all, libcompiler-rt has a bunch of test failures, etc. Alternatively, can I disable these components in the CMake build locally? >>>> >>>> Yes, go ahead and use the autoconf build. >>>> >>>> Can you send a patch to test-release.sh that makes this default for >&g...

Hello there, I recently started working on the LLVM backend for a target that doesn't support x87 instructions. Currently, I am in the process of completely disabling some x87 instructions such as fcomi, fcompi,... for a specific sub-target. I also do not have SSE enabled for my sub-target, and llvm resorts to fcomi* instructions for FP compare instructions. Is there a way to bypass the

On 19 Jan 2018, at 17:11, Hans Wennborg <hans at chromium.org> wrote: > > On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: >> On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >>> >>> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>>> On 17 Jan 2018, at 18:53, Hans Wennborg

...>>> questions, etc. >>>> >>>> The tracking bug for release blockers is PR24126. >>> >>> Is it OK to do an autoconf build? The CMake build tries to build various components which do not yet work on FreeBSD, e.g. libcxxabi does not compile at all, libcompiler-rt has a bunch of test failures, etc. Alternatively, can I disable these components in the CMake build locally? >> >> Yes, go ahead and use the autoconf build. >> >> Can you send a patch to test-release.sh that makes this default for >> FreeBSD? It's already t...

On Thu, Jan 18, 2018 at 7:27 PM, Dimitry Andric <dimitry at andric.com> wrote: > On 18 Jan 2018, at 15:03, Jonas Hahnfeld <hahnjo at hahnjo.de> wrote: >> >> Am 2018-01-18 14:55, schrieb Dimitry Andric via llvm-dev: >>> On 17 Jan 2018, at 18:53, Hans Wennborg via Release-testers >>> <release-testers at lists.llvm.org> wrote: >>>> Start

Dear testers, 3.7.0-rc1 was just tagged; please start your testing engines :-) Upload binaries to the sftp and report your results to this thread. I'm sorry for the delay between branching and tagging. The changes to the release script took a little longer than I hoped. Thanks for helping with the release, and do let me know of any issues, questions, etc. The tracking bug for release