[llvm-commits] CommandLine.html patch

27;m very new to LLVM, so I can only guess at how DOUT is related to DEBUG(). Is there another example that would be more straightforward? Thanks, Sam Bishop CommandLine.html.patch Description: Binary data ___ llvm-commits mailing list llvm-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits

Re: [llvm-commits] CommandLine.html patch

On Wed, January 9, 2008 10:34 am, Sam Bishop wrote: > Also, I was confused by one of the examples regarding the handling of > program-wide global options such as a debug flag > ... > I'm very new to LLVM, so I can only guess at how DOUT is related to DEBUG(). > Is there anothe

[llvm-commits] fix for a compile error?

d()'s eighth argument to be llvm::MVT::ValueType. This seems to better fit the intentions of the original author, but it bothers me that I don't understand why the compiler was complaining about the original code. A tr

[llvm-commits] Makefile.rules patch: remove redundant -I compiler flags

The attached patch makes VERBOSE builds easier to wade through. It's likely to also permute the PROJ_* and LLVM_* includes, but I don't think that should matter. I've done a full-tree compile and everything seems to be working. Thanks, Sam Bishop *** Before *** [EMAIL

Re: [llvm-commits] [llvm] r46432 - /llvm/trunk/Makefile.rules

Hi, Duncan. On Mon, January 28, 2008 6:48 am, Duncan Sands wrote: > This breaks the build when the objects directory is different to the > source directory. I'm very sorry about this. The attached patch will fix it. Thanks, Sam Bishop Makefile.rules.patch Description:

[llvm-commits] patches for the JIT and Kaleidoscope tutorials

Every page has been given the "next link" treatment, but otherwise I'm only half way through the Kaleidoscope tutorial. I will send a follow-on patch if time permits. Thanks, Sam Bishop tutorial.patch Description: Binary data ___ llvm-