search for: compiler_rt

Hi; This is on Linux/x86-64, I get this at stage1: make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt' Makefile:6: make/config.mk: No such file or directory Makefile:7: make/util.mk: No such file or directory Makefile:16: *** Refusing to build with empty ProjObjRoot variable. Stop. make[2]: Leaving directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt' make[1]: *** [all]...

Hi All, I just wanted to let you know that libc++ and compiler_rt and now dual licensed under *both* the UIUC and MIT license. The reason for this is that the UIUC license (like many BSD licenses) requires that binaries that link LLVM code contain a notice that they are derived from LLVM. This clause doesn't make sense for libraries like libc++ and compiler...

ping? Still fails on 3.1 branch. On Tue, Apr 17, 2012 at 5:35 PM, İsmail Dönmez <ismail at namtrac.org> wrote: > > Hi; > > This is on  Linux/x86-64, I get this at stage1: > > make[2]: Entering directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt' > Makefile:6: make/config.mk: No such file or directory > Makefile:7: make/util.mk: No such file or directory > Makefile:16: *** Refusing to build with empty ProjObjRoot variable.  Stop. > make[2]: Leaving directory `/home/abuild/rpmbuild/BUILD/llvm/stage1/projects/compiler_rt'...

...nisation > - Run a script to filter some of your changes into that one I don’t know why you think there is a need for a script, or why it is different from today. Let say I’m working on a fork of the compiler-rt read-only repo and I want to upstream a patch at some point: Today: - cd /path/to/compiler_rt-forked - git format-patch … - cd /path/to/compiler_rt-upstream - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch - git svn dcommit - done Tomorrow with a monorepo: - cd /path/to/compiler_rt-forked - git format-patch … - cd /path/to/unifiedrepo-upstream - git am /path/to/compile...

...nly functionality I'm interested in is being able to reset the counters, get the size of the data, and dump the data into a memory buffer. I have to admit I haven't been able to find a lot of documentation about how this data is stored inside of the different sections, but with the code in compiler_rt/libs/profile I've been able to craft something that seems to do something sensible. I have however a couple of questions: - The "Values" field in __llvm_profile_data always seems to be NULL. Is this expected? What/why could cause this? - The fields in the NumValueSites array i...

...f your changes into that one > > I don’t know why you think there is a need for a script, or why it is > different from today. > Let say I’m working on a fork of the compiler-rt read-only repo and I want > to upstream a patch at some point: > > Today: > > - cd /path/to/compiler_rt-forked > - git format-patch … > - cd /path/to/compiler_rt-upstream > - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch > - git svn dcommit > - done > > Tomorrow with a monorepo: > > - cd /path/to/compiler_rt-forked > - git format-patch … > - cd /...

...; >> I don’t know why you think there is a need for a script, or why it is >> different from today. >> Let say I’m working on a fork of the compiler-rt read-only repo and I want >> to upstream a patch at some point: >> >> Today: >> >> - cd /path/to/compiler_rt-forked >> - git format-patch … >> - cd /path/to/compiler_rt-upstream >> - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch >> - git svn dcommit >> - done >> >> Tomorrow with a monorepo: >> >> - cd /path/to/compiler_rt-forked &...

I need to correct myself. It is possible to cross compile it on Windows, but not using the provided build systems. On Sun, Mar 29, 2015 at 12:52 PM, Daniel Dilts <diltsman at gmail.com> wrote: > I asked about this same question in the past (month or three ago). It is > not possible to cross compile compiler-rt on Windows. If you want to cross > compile you should use the make

...organisation - Run a script to filter some of your changes into that one I don’t know why you think there is a need for a script, or why it is different from today. Let say I’m working on a fork of the compiler-rt read-only repo and I want to upstream a patch at some point: Today: - cd /path/to/compiler_rt-forked - git format-patch … - cd /path/to/compiler_rt-upstream - git am /path/to/compiler_rt-forked/0001-My-awesome-changes.patch - git svn dcommit - done Tomorrow with a monorepo: - cd /path/to/compiler_rt-forked - git format-patch … - cd /path/to/unifiedrepo-upstream - git am /path/to/compile...

...t; > reset the counters, get the size of the data, and dump the data into a > > memory buffer. > > > > I have to admit I haven't been able to find a lot of documentation > > about how this data is stored inside of the different sections, but > > with the code in compiler_rt/libs/profile I've been able to craft > > something that seems to do something sensible. > > > > I have however a couple of questions: > > > > - The "Values" field in __llvm_profile_data always seems to be NULL. > > Is this expected? What/why cou...

...39; -DBAREMETAL_ARMV7EM_SYSROOT=~/arm-sysroot -C > path/to/copy/of/edited/BaremetalARM.cmake path/to/llvm > > Where your path/to/llvm has the symlinks: > > * path/to/llvm/tools/clang -> path/to/clang ln -s `which clang40` path/to/llvm/tools/clang > * path/to/llvm/runtimes/compiler_rt path/to/compiler_rt ln -s path/to/llvm/projects/compiler-rt path/to/llvm/runtimes/compiler_rt Is that right? > > And by "edited BaremetalARM.cmake" I mean you can strip out the other > targets in there that you don't need. So I have copied BaremetalARM.cmake into llvm/cma...

...or: unable to find library -lclang_rt.builtins-armv6m.a clang-5.0: error: ld.lld command failed with exit code 1 (use -v to see invocation) makefile:33: recipe for target 'main' failed make: *** [main] Error 1 2) To get clang_rt.builtins-armv6m.a or libc, libm, I tried to build LLVM/Clang (compiler_rt) from LLVM/Clang source following this - http://llvm.org/docs/HowToCrossCompileLLVM.html but I got this error, TARGET_TRIPLE=arm-none-eabi MYHOSTBIN=${HOME}/clang/source/build_x64/bin MYGNUARM_ROOT=${HOME}/opt/gcc-arm-none-eabi-6-2017-q2-update MYCFLAGS="--specs=nosys.specs -mcpu=cortex-m4 -mt...

...to commit. There has been universal support for merging it in, so lets do it. Please start by commiting the llvm part (i.e. lib/Target/ARM64, tests, etc). We should have a similar discussion on cfe-dev to get those changes reviewed, and commit the clang pieces when that settles out. The libc++, compiler_rt, and lldb piece should be separately reviewed and explained before they go in. Thanks Bob (and everyone who worked on the apple arm64 backend!) -Chris

So, I remember we discussed this earlier this year, but I can't find the thread. The idea is to move libunwind into compiler-rt for the simple reasons below: 1. Unwinding is not exclusive to C++, nor exception handling. 2. Clang still includes libgcc_s and libgcc_eh when using compiler-rt (maybe eh isn't needed, but it was there for libgcc). 3. Testing the libunwind with libc++ on ARM is

On 29 Jul 2016, at 05:11, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > What I meant by “different problem" is that “downstream users” for instance don’t need to commit, that makes their problem/workflow quite different from an upstream developer (for instance it is fairly easy to maintain a read-only view of the existing individual git repo currently on

...Bug 21560 - Add support to cmake for using installed versions of LLVM and Clang - Takumi commented that this works. * Bug 21561 - Update release scripts to use CMake - Still outstanding and blocking removal of autoconf * Bug 21562 - Add a CMake equivalent for make/platform/clang_darwin.mk in compiler_rt - From discussions on llvm-dev and IRC the proper fix for this is a cross-compiling approach for compiler_rt builds, and this is a blocker. * Bug 21568 - Cannot add rpath - It looks like this is not a blocker because it can be done, but is unwieldy. I think this may be made a lot easier with h...

On 22 October 2014 19:24, Jonathan Roelofs <jonathan at codesourcery.com> wrote: > I do compiler_rt + libc++abi + libc++ + clang (with a custom ToolChain) testing > of libc++ on bare-metal ARM.... so it is possible. Perhaps you mean to say that > it's not possible to test libunwind on arm-linux when using compiler_rt? Yeah, it's hard and clumsy, not impossible. Basically, I want t...

...more of the involved developers > (as much as I may prefer an alternate solution). Last time we brought this up, there was only partial consensus, and then someone arbitrarily declared total consensus (without compelling arguments in any particular direction) that we were going to move it to compiler_rt. Then the discussion fell on the floor because no-one had time to actually do the move. Please, let's not let that happen again this time. Cheers, Jon > > -- > Saleem Abdulrasool > compnerd (at) compnerd (dot) org -- Jon Roelofs jonathan at codesourcery.com CodeSourcery / Men...

..., >> but not using the provided build systems. > > > Hi Daniel, > > Thanks for helping. I'm using ubuntu 14.04 x86_64 system. I've tried cmake > for couple of days until I give up. You are right, using 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",...

...LinkerDriver::link(ArrayRef<const char *> ArgsArr) { // Write the result. writeResult(&Symtab); - - // Call exit to avoid calling destructors. - exit(0); } } // namespace coff I'm getting this error from LLVM: unable to write object file c:\msys64\home\andy\zig\zig-cache\compiler_rt.obj: The requested operation cannot be performed on a file with a user-mapped section open. The same process calls LLD with this .obj as a linker input file, then tries to write to the same .obj file later. I believe LLD is mmapping the .obj file and then not cleaning it up. Can I have some gui...