Displaying 20 results from an estimated 8000 matches similar to: "Unable to verify of llvm sources with the .sig files"
2019 Apr 04
2
Unable to verify of llvm sources with the .sig files
With the new signature file I was able to verify, but there was
still a bad signature: "gpg: key 0x0FC3042E345AD05D: 1 bad signature"
which I highlighted below. Didn't seem to be a problem, but thought
I'd point it out. I'd be glad to do additional tests if you'd like.
$ gpg --list-keys
/home/wink/.gnupg/pubring.kbx
-----------------------------
pub
2016 Sep 06
5
Recommended computer resources to build llvm
And again...
LLVM_BUILD_LLVM_DYLIB:BOOL=ON
LLVM_LINK_LLVM_DYLIB: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>
2016 Sep 13
2
-fsanitize=memory failing on 3.9.0
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
2016 Sep 06
2
Recommended computer resources to build llvm
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
2016 Sep 06
10
Recommended computer resources to build llvm
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
2016 Sep 11
2
-fsanitize=memory failing on 3.9.0
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
2019 Apr 28
2
How to submit a change for code review using arc
> 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
2006 Feb 28
3
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
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 /opt/llvm-1.6/llvm-gcc/lib/libcrtend.a
2016 Sep 12
2
-fsanitize=memory failing on 3.9.0
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
2017 May 24
3
Status of move to github
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:
2006 Feb 11
2
[LLVMdev] hello. seg faults on AMD64 linux
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 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
2019 Apr 26
2
How to submit a change for code review using arc
I've gone through Code Reviews with Phabriactor[1], Arcanist Quick
Start[2] and Arcanist User Guide arc diff[3]. But I'm unable to setup
reviewers my editor pops up and there is a "Reviewers:" line and but
I'm unable email addresses directly. It seems it wants reviewers
passed on the command line or some how in .arcconfig.
But I haven't been able to find any
2016 Sep 07
4
Test failures building RELEASE_3.9.0/final
I've "successfully" built 3.9.0 release but when I run "ninja check-all" I
got 208 Unexpected failures:
Expected Passes : 33997
Expected Failures : 198
Unsupported Tests : 685
Unexpected Failures: 208
Below is the log I captured running "time ninja check-all | tee
ninja-check-all.txt"
https://drive.google.com/open?id=0B-KTY7zi7eZHU2hGYTRtd01QZjA
2006 Feb 28
1
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
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 'crtend' missing
2006 Feb 11
2
[LLVMdev] LLVM language atomic and syscall/int instructions
Hello,
In reading the language reference manual I don't see any capability to
perform atomic operations 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,
2006 Mar 05
1
[LLVMdev] Possible solution to a llvm-ld bug
Hello,
As previously mentioned I had a linking problem using llvm-ld
(http://lists.cs.uiuc.edu/pipermail/llvmdev/2006-February/005246.html)
I was getting a error if I used -L switch when linking using the following command line:
llvm-ld -o t1.app t1.bc t1.a -L/opt/llvm-1.6/llvm-gcc/lib -lcrtend
I believe I've tracked down the problem; in the "main" of tools/llvm-ld.cpp
the
2006 Feb 28
1
[LLVMdev] Leading spaces in Makefile.rules
Hello,
Last night I checked out the head of CVS and tried to 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
2006 Feb 27
2
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
Hello,
When I compile a "hello.c" program with a printf in "main" and use
llvm-gcc with a "-c" option:
llvm-gcc -c t1.c -o t1.bc
and then try to compile t1.bc to native using llc & gcc I get a call to
"__main" which is undefined.
If I don't use the "-c" option:
llvm-gcc t1.c -o t1
I don't get a reference to
2006 Feb 28
0
[LLVMdev] Using llvm-gcc with a simple program and the '-c' option
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 'crtend' missing
>
You didn't get the instructions quite right. The option is
2016 Sep 07
2
Test failures building RELEASE_3.9.0/final
I ran "ninja check-asan" and no errors. But "ninja check-msan" had 117
errors.
I took the first FAILED test, which was for eventfd.cc, and executed the
command
line creating an eventfd executable in a temporary directory and then
executed that file using gdb. Finally, used bt to dump the stack.
I've emailed llvm-admin at lists.llvm.org to setup an account since