similar to: How to submit a change for code review using arc

On Thu, Apr 25, 2019 at 8:32 PM Doerfert, Johannes <jdoerfert at anl.gov> wrote: > > The username has to exist on phabricator: > https://reviews.llvm.org/p/peterc/ -> 404 > https://reviews.llvm.org/p/evgeniys/ -> 404 > > I'm guessing you want: > https://reviews.llvm.org/p/daemon/ -> Evgeniy > https://reviews.llvm.org/p/pcc/ -> Peter Collingbourne

> 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

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

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

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

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>

Hi, I recently tried reviewing/committing some of my code on Phabricator/Arcanist for the first time and I noticed that the docs [1] ask for feedback, so here it is! Phabricator functions reasonably well and it is a lot easier to write comments and respond to comments on particular parts of code as opposed to the old way of copy and pasting patches into e-mails sent to llvm-commits. Two minors

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

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

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

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

Forgot to mention: > Also, how would arcanist pick up two callsigns here? Wouldn't it just pick the from the closest surrounding .arcconfig? The review request will belong to a single repository, as you noticed (from the closest .arcconfig to where the arc command was invoked). However, when commits land, they will be imported under either one (rL for LLVM diffs) or two (rL + rC for e.g.

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

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

Hi Ben, (+llvm-dev since the email I'm replying to wasn't sent there) 2017-11-21 17:18 GMT+01:00 Ben Hamilton via cfe-dev <cfe-dev at lists.llvm.org> : > OK. I confirmed that Stephan's process to send out cross-repo diffs from > the monorepo is not affected by my proposal. > > I'm a bit late to the party, and I might just not have comprehended this correctly.

Thanks for the catch Dead! I'll send out patches to update .arcconfig files to use https. On Thu, Jul 14, 2016 at 3:22 PM Dean Michael Berris <dberris at google.com> wrote: > Thanks Eric, > > If you're like me who started doing this and found some weird errors, you > may have to do the following instead: > > $ arc install-certificate

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

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

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:

It seems like this has already been set up for all the projects except for libunwind. Can we create a Differential repository for it as well? I'll be happy to update its .arcconfig once that's done. On Mon, Nov 27, 2017 at 9:02 AM Ben Hamilton via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Forgot to mention: > > > > Also, how would arcanist pick up two callsigns