search for: saville

...LIB:BOOL=ON This one is the good one... maybe. On Tue, Sep 6, 2016 at 11:35 PM, Alexandre Isoard < alexandre.isoard at gmail.com> wrote: > That is because I mistyped it: > LLVM_ENABLE_LLVM_DYLIB:BOOL=ON > LLVM_LINK_LLVM_DYLIB:BOOL=ON > > On Tue, Sep 6, 2016 at 11:31 PM, Wink Saville <wink at saville.com> wrote: > >> On Tue, Sep 6, 2016 at 3:05 PM, Alexandre Isoard >> <alexandre.isoard at gmail.com> wrote: >> > LLVM_ENABLE_DYLIB >> >> Where/when/how do you specify LLVM_ENABLE_DYLIB and LLVM_LINK_DYLIB? >> >> I tried th...

I've updated the arch linux bug (https://bugs.archlinux.org/task/50385) with a patch for glibc in the arch linux packages that does fix the segment fault for me. On Mon, Sep 12, 2016 at 2:08 PM, Renato Golin <renato.golin at linaro.org> wrote: > On 12 September 2016 at 22:02, Wink Saville <wink at saville.com> wrote: >> I then cloned the gcc 2.24 sources as of today and the code that >> 24e2b1cede1952d7d4411a3cafd25dd8593dab9f reverts is still there. I >> also took a quick look at the Arch Linux glibc package >> (https://git.archlinux.org/svntogit/packa...

...nal tests if you'd like. $ gpg --list-keys /home/wink/.gnupg/pubring.kbx ----------------------------- pub rsa4096/0x9F79B9CEB03232F9 2018-04-18 [C] [expires: 2019-04-18] Key fingerprint = 0B15 37E2 6423 4EF7 7934 7A79 9F79 B9CE B032 32F9 uid [ultimate] Winthrop Lyon Saville III <wink at saville.com > sub rsa4096/0xD232788D248BCF0E 2018-04-18 [S] [expires: 2019-04-18] sub rsa4096/0x9220D48FF6008D0D 2018-04-18 [E] [expires: 2019-04-18] sub rsa4096/0x92BB19D0D4F68457 2018-04-18 [A] [expires: 2019-04-18] pub rsa2048/0x7F2D434B9741E8AC 2011-04-10 [SC]...

...o compile after configuring with: ./configure --enable-debug-runtime --enable-jit --prefix=/opt/lvm-cvs I then got a message indicating that Line 1099 of Makefile.rules has 8 leading spaces instead of a tab, I fixed that and then the build completed, although there were 6 warnings (http://www.saville.com/llvm/make1.out). Reid suggested here (http://lists.cs.uiuc.edu/pipermail/llvmdev/2006-February/005261.html) that I install new runtime bytecodes. I did and then did: make clean ; make And got 4 warnings here (http://www.saville.com/llvm/make2.out). Maybe the warnings are normal, just...

Please do the bisect, nice to hear it recently worked! At this point I built mean with debug and its failing with initializing a LFStack doing an atomic operation, IIRC. On Sun, Sep 11, 2016, 9:09 AM Renato Golin <renato.golin at linaro.org> wrote: > On 7 September 2016 at 18:41, Wink Saville via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Further more, there is a bug reported concerning a seg fault when > > using msan on Arch Linux (https://bugs.archlinux.org/task/50385) so > > I'm not the only person in the world have a problem. > > I'm...

On Tue, Sep 6, 2016 at 3:05 PM, Alexandre Isoard <alexandre.isoard at gmail.com> wrote: > LLVM_ENABLE_DYLIB Where/when/how do you specify LLVM_ENABLE_DYLIB and LLVM_LINK_DYLIB? I tried the following on the cmake command line: $ cmake -G Ninja .. -DCMAKE_INSTALL_PREFIX=/home/wink/opt/llvm -DLLVM_ENABLE_DYLIB=true -DLLVM_LINK_DYLIB=true And got: ... -- Performing Test

...and lli hello.bc works fine but when I convert it to hello.native it seg faults. AMD64 machine uname -a: Linux hp5kuw 2.6.12-10-amd64-k8 # Mon Jan 16 17:23:13 UTC 2006 x86_64 GNU/Linux llvm-gcc --version outputs: llvm-gcc (GCC) 3.4-llvm 20051104 (LLVM 1.6) What have I done wrong? Wink Saville

...quot;, "evgeniys": "eugeni.stepanov at gmail.com", "llvm-commits": "llvm-commits at lists.llvm.org" } } My commit message is: $ git log -1 commit f04a938e5ad72afbf64242718d456fa480ad5f6b (HEAD -> compiler-rt-fix-cmake-warnings) Author: Wink Saville <wink at saville.com> Date: Tue Apr 23 16:55:21 2019 -0700 [compiler-rt] Fix cmake warnings Summary: - Fix cmake BOOL misspellings - Set cmake policy for CMP0075 to NEW Reviewers: peterc, evgeniys Subscribers: llvm-commits The result of "arc diff master&qu...

I've looked at the version of libc I have and its 2.24: $ /lib/libc.so.6 GNU C Library (GNU libc) stable release version 2.24, by Roland McGrath et al. I then cloned the gcc 2.24 sources as of today and the code that 24e2b1cede1952d7d4411a3cafd25dd8593dab9f reverts is still there. I also took a quick look at the Arch Linux glibc package

> While it's still fresh in your mind, you might consider updating https://llvm.org/docs/Phabricator.html (which is llvm/docs/Phabricator.rst) based on your experience, > which will make it easier for future contributors. I guess the main issue is getting used to the fact that Phabricator user names are independent and must be looked up on the web site -- at least I haven't found

I've got a i7 with 12 logical cores and 16GB of RAM I successfully built RELEASE_390/final but for the last 100 or so files I'd to use "ninja -j2" so as not to keep from swapping in the best case and and in the worst case the build kills itself without completing because apparently its run out of memory. For the first 3200 files or so it was doing just fine with

That last post I see on this mailing list is from November <http://lists.llvm.org/pipermail/llvm-dev/2016-November/106941.html> concerning the results of the survey. So I was wondering what the latest status for moving to github? -- Wnk -------------- next part -------------- An HTML attachment was scrubbed... URL:

...ations or issue sys calls and or software interrupts. I see here, http://gcc.gnu.org/ml/gcc/2005-11/msg01031.html, that Anthony asked about atomic operations but I didn't see an answer. Regarding syscall I see some discussions but no explanation of why it wasn't included. Cheers, Wink Saville

There is no x86_64 code generator at this time. Wink Saville wrote: > Hello, > > I've installed LVM 1.6 and followed the getting started instructions > and lli hello.bc works fine but when I convert it to hello.native it > seg faults. > > AMD64 machine uname -a: > > Linux hp5kuw 2.6.12-10-amd64-k8 # Mon Jan 16 17:23:13 UTC...

...ed down the problem; in the "main" of tools/llvm-ld.cpp the call to ParseCommandLineOptions is after the TheLinker.addPaths(LibPaths) statement so the -L command line parameter is ignored. My fix was to move the ParseCommandLineOptions to the beginning of the main routine. Cheers, Wink Saville

Chris Lattner wrote: > On Sun, 26 Feb 2006, Wink Saville wrote: >> I then do the following in my makefile: >> >> llvm-gcc -c t1.c -o t1.bc >> llvm-gcc -c t1sub1.c -o t1sub1.bc >> llvm-gcc -c t1sub2.c -o t1sub2.bc >> llvm-ar r t1.a t1sub1.bc t1sub2.bc >> llvm-ar: creating t1.a >> llvm-ld -o t1.app t1.bc t1.a...

...ot; option: llvm-gcc t1.c -o t1 I don't get a reference to "__main" and I can compile to native without problem. Also, I created some simple modules without a "main" and using the "-c" option and that works as expected. What am I doing wrong? Thanks, Wink Saville

I'm on an Arch Linux system: $ uname -a Linux wink-desktop 5.0.4-arch1-1-ARCH #1 SMP PREEMPT Sat Mar 23 21:00:33 UTC 2019 x86_64 GNU/Linux My gpg version is: $ gpg --version gpg (GnuPG) 2.2.15 libgcrypt 1.8.4 Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later < https://gnu.org/licenses/gpl.html> This is free software: you are free to change and

Misha Brukman wrote: > On Sun, Feb 26, 2006 at 10:00:18PM -0800, Wink Saville wrote: > > [snip] > If you're using -c, you're telling LLVM that there are other modules you > will link into the executable. Thus, LLVM does not know whether there > will be static ctors/dtors to run or not, so there's the call to > __main() from main. > &gt...

Reid Spencer wrote: > On Mon, 2006-02-27 at 20:43 -0800, Wink Saville wrote: > >>> Try passing "-L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend" to llvm-ld. >>> >> This didn't work for me: >> llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib/ -lcrtend.a >> >> I get two warning's about library ...