similar to: [LLVMdev] CVS in Web Pages

I know this process is well documented here http://llvm.org/docs/GettingStarted.html But man do I love scripting things: LLVM Getting Started (See http://llvm.org/docs/GettingStarted.html) ./getttingStarted.sh [-clang] [-compiler-rt] [-test-suite] [-branch branch] [-dir path] [-r rev] By default this script checks out ToT LLVM to the current working directory Project Options: -clang

I tried to access the latest LLVM, since several messages here so far have referred me to it. Now I have no experience with CVS-over-the-net. My previous experiences with versoin control have been RCS and Monotone. Brief summary: hendrik at lovesong:~/dv$ mkdir llvm hendrik at lovesong:~/dv$ cd llvm hendrik at lovesong:~/dv/llvm$ cvs -d :pserver:anon at llvm.org:/var/cvs/llvm login Logging in

Hi Joe, thanks for working on this. My honest opinion on it is that time would be better spent improving the documentation, as the current documentation is archaic. I think this has come up on the list before, but to rehash: * Start out by saying "LLVM can be built with make or CMake, and checked out with svn or git", and have "make", "CMake", "svn", and

On May 10, 2008, at 7:55 PM, kr512 wrote: >> You are seriously ignorant of what LLVM is all about. >> Please go inform yourself. > > Alright, I read some more on llvm.org and it confirmed what > I was saying: > http://www.llvm.org/docs/GettingStarted.html#tutorial > > See at the end where it says: > ----------- > 6.Compile the program to native assembly using

A debug or release build? -bw On Sep 24, 2007, at 2:36 PM, Dale Johannesen wrote: > > On Sep 24, 2007, at 2:29 PM, Bill Wendling wrote: > >> Hi all, >> >> Did someone forget to check-in a patch? I'm getting this error during >> compilation on PPC: > > A recent checkout compiled fine for me (on x86). > >>

Hi! What's the plan for support on Linux 64-bit machines? Is that actively being worked on right now or is there a roadmap for doing this? Thanks! -bw

Hendrik, You could also just "touch ~/.cvspass" to create the file which should eliminate the warning. However, since you did a login, and it seemed successful, chances are the file now exists (containing the blank password for anon at llvm.org). Reid. On Mon, 2006-08-07 at 09:14 -0500, John Criswell wrote: > Hendrik Boom wrote: > > I tried to access the latest LLVM, since

On Dec 13, 2010, at 10:26 AM, Yuri wrote: > Here http://llvm.org/docs/GettingStarted.html#requirements FreeBSD/amd64 > isn't mentioned. It works quite fine for me. > Yes, it should. I fixed that. Thanks! > Also, it mentions that its known to work on Solaris/V9(Ultrasparc). > Isn't this wrong since JIT isn't currently working on Sparc and is only > expected to

Hendrik Boom wrote: > I tried to access the latest LLVM, since several messages here so far have > referred me to it. Now I have no experience with CVS-over-the-net. My > previous experiences with versoin control have been RCS and Monotone. > > Brief summary: > > hendrik at lovesong:~/dv$ mkdir llvm > hendrik at lovesong:~/dv$ cd llvm > hendrik at lovesong:~/dv/llvm$

Hi, I noticed that the LLVM 3.5 release branch landed recently. I have a few patches (these are all part of my recent work to fix up the CMake interface) that I'd like in both LLVM3.5 release branch and trunk that I'd like to commit Is there any policy on how should do this be done, or can I just commit the patch to both trunk and then the release branch with identical commit messages?

On Mon, 07 Aug 2006 09:26:07 -0700, Reid Spencer wrote: > Hendrik, > > You could also just "touch ~/.cvspass" to create the file which should > eliminate the warning. However, since you did a login, and it seemed > successful, chances are the file now exists (containing the blank > password for anon at llvm.org). Indeed, the file is there. > > Reid. >

Here http://llvm.org/docs/GettingStarted.html#requirements FreeBSD/amd64 isn't mentioned. It works quite fine for me. Also, it mentions that its known to work on Solaris/V9(Ultrasparc). Isn't this wrong since JIT isn't currently working on Sparc and is only expected to work with MC project completion? Sparc should me mentioned in the 'partial support' table. Also, I think

FYI: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/066389.html Please read and let me know you comments. -bw On Oct 11, 2013, at 2:47 PM, Dmitry Babokin <babokin at gmail.com> wrote: > Looking forward to these changes! Thanks for working on it. > > > On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I

Hello all, According to: http://llvm.org/releases/2.8/docs/GettingStarted.html#checkout folks can check out a specific release from Subversion. As of right now, RELEASE_28 contains folders for each of the release candidates, as opposed to the final content. Same goes for Clang. -Matt -------------- next part -------------- An HTML attachment was scrubbed... URL:

Looking forward to these changes! Thanks for working on it. On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I can try my best, but it would be a bit tricky to get it all finished by > then... > > -bw > > On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > Bill, > > Are there

The third 3.5 release candidate is now available. Please pick up sources and binaries here: https://llvm.org/pre-release/3.5 Run it through its phases and report any bugs you find! Share and enjoy! -bw

On Aug 15, 2009, at 5:05 PM, Erick Tryzelaar wrote: > I just tried to compile llvm-gcc against the top of llvm and I ran > into this error: > > /.../llvm/llvm-gcc-build/./prev-gcc/xgcc > -B/.../llvm/llvm-gcc-build/./prev-gcc/ > -B/.../llvm/llvm-gcc-install/x86_64-unknown-linux-gnu/bin/ -c > -DHAVE_CONFIG_H -g -O2 -I. > -I/.../llvm/llvm-gcc-4.2/libiberty/../include -W

On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > On Sep 24, 2007, at 3:07 PM, Bill Wendling wrote: > >> A debug or release build? >> >> -bw > > Both, actually. Weird. I see a potential problem, though. The code is like this: void dumpToDOUT(SparseBitVector<> *bitmap) { dump(*bitmap, DOUT); } where dump expects an llvm::OStream& for the

On Sep 24, 2007, at 2:29 PM, Bill Wendling wrote: > Hi all, > > Did someone forget to check-in a patch? I'm getting this error during > compilation on PPC: A recent checkout compiled fine for me (on x86). > /Volumes/SandBox/Clean/llvm-9999-01.roots/llvm-9999-01~obj/src/llvm/ > lib/Analysis/IPA/Andersens.cpp: > In function 'void

Hi, Bill - On Wed, Jun 01, 2005 at 10:33:39AM -0400, Bill Wendling wrote: > What's the plan for support on Linux 64-bit machines? Is that actively > being worked on right now or is there a roadmap for doing this? Do you mean compiling on 64-bit Linux or generating code for 64-bits? As you can see here: http://llvm.cs.uiuc.edu/docs/GettingStarted.html#hardware