similar to: [LLVMdev] Antw.: 2.0 Pre-release tarballs online

Hello, Bram > * It seems that a C-call like printf("---\n") is transformed to puts > ("---") in the LLVM IR instead of keeping it a printf. What are the > circumstances in which this happens? Do other similar conversions > occur? Can this be turned off (lower optimisation level?)? Manually > replacing the puts-calls by a printf-call is not

On Sat, 19 May 2007, Anton Korobeynikov wrote: >> * It seems that a C-call like printf("---\n") is transformed to puts >> ("---") in the LLVM IR instead of keeping it a printf. What are the >> circumstances in which this happens? Do other similar conversions >> occur? Can this be turned off (lower optimisation level?)? Manually >> replacing the

Hi, Op 18-mei-07, om 18:40 heeft Reid Spencer het volgende geschreven: > What goes wrong? Everything's fine now. Forgot to look at Tanya's changes (#include "llvm/Support/DataTypes.h") :-)... > Glad you figured that out. The build guidelines for llvm-gcc are in > README.LLVM at the top level of the llvm-gcc source tree. It > recommends > making links. Some

On Sun, 20 May 2007, Bram Adams wrote: > Op 19-mei-07, om 00:39 heeft Chris Lattner het volgende geschreven: >> Anton is right. You should be able to use -fno-builtins to disable >> this. > > Thanks, that did the trick. > > Some final remarks (my app works again :-)): > * llvm.va_start and similar intrinsics now have an i8* arg instead > of an sbyte** ok >

Hi Bram, On Fri, 2007-05-18 at 18:12 +0200, Bram Adams wrote: > Hi, > > Op 18-mei-07, om 10:10 heeft Tanya M. Lattner het volgende geschreven: > > >> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build > >> with the header files using uintptr_t (not recognised as a type). > >> Putting "#include <stdint.h>" in

On Thu, 17 May 2007, Bram Adams wrote: > About LTO support: the new release documents don't mention anything about > this. Also, the relevant bugzilla entries I could find date back to March > 2007. Has any progress been made recently in adding LTO to the Darwin linker > and/or GNU binutils? I'll mention this in the release notes. The darwin linker in 10.5 (not yet

On Tue, 22 May 2007 23:52:46 -0700 (PDT) Chris Lattner <sabre at nondot.org> wrote: >On Sun, 20 May 2007, Bram Adams wrote: >> On a related note: while using llvmc I have some test cases where the >> following error now pops up on Linux X86 (not on OSX): >> >> <premain>: CommandLine Error: Argument 'debug' defined more than once! >> llvmc:

Hi, Op 19-mei-07, om 00:39 heeft Chris Lattner het volgende geschreven: > Anton is right. You should be able to use -fno-builtins to disable > this. Thanks, that did the trick. Some final remarks (my app works again :-)): * llvm.va_start and similar intrinsics now have an i8* arg instead of an sbyte** * For some reason the Arguments of a Function are now circularly linked,

Hi, Op 18-mei-07, om 10:10 heeft Tanya M. Lattner het volgende geschreven: >> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build >> with the header files using uintptr_t (not recognised as a type). >> Putting "#include <stdint.h>" in include/llvm/BasicBlock.h (llvm) >> and in "include/llvm/ValueSymbolTable.h" (frontend)

> On Slackware 10.2 (GCC 3.3.6), I got an error during a debug build with the > header files using uintptr_t (not recognised as a type). Putting "#include > <stdint.h>" in include/llvm/BasicBlock.h (llvm) and in > "include/llvm/ValueSymbolTable.h" (frontend) resolved this. Ok. This is now fixed on the release branch. Thanks! > Also, I got linking

Hi, Op 15-mei-07, om 10:23 heeft Tanya M. Lattner het volgende geschreven: 1) Download llvm-gcc4 binary and llvm. Compile and run make check. I did a debug build on OSX 10.4.9 and everything went fine. Results of "make check" (see ppc.log): === Summary === # of expected passes 1630 # of unexpected failures 21 # of expected failures 2

Hello, Bill > It may be my lack of understanding, but it appears that having -- > enable-eh set during compilation of llvm-gcc is causing extra files > to be compiled. Oh, no. They are always compiled. > They do. However, it doesn't seem to stop it from failing during > compilation of unwind-dw2.c for libgcc -- it has > "__builtin_eh_return" in it. During

On Tue, May 15, 2007 at 01:23:32AM -0700, Tanya M. Lattner wrote: > 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make > ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. > > It would also be helpful for someone to compile/test with objdir != srcdir. This is on FreeBSD 6.2-RELEASE, on i386. Both llvm and llvm-gcc were compiled with objdir

On Thu, May 17, 2007 at 10:11:51PM -0700, Tanya M. Lattner wrote: > > On Tue, May 15, 2007 at 01:23:32AM -0700, Tanya M. Lattner wrote: > >> 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make > >> ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. > >> > >> It would also be helpful for someone to compile/test with

On Fri, 18 May 2007, Emil Mikulic wrote: > > CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3000.12-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf34 Stepping = 4 > Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C > MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> >

Hi Anton, You're already a part of the llvm development team by participating actively on the llvm development list :) If you wish we can put you on: http://llvm.cs.uiuc.edu/Developers.html Great to have you on the team, welcome! We (Jeff, Morten, Paolo, the rest of the team and I) are looking forward to cooperate with you and to push win32 and mingw versions even further to stable and

I've updated the pre-release tarballs online. I'm also extending the testing completion date to May 22nd at 5pm PDT. The new release target date is May 23rd. If you have any free time, please give the new pre-release a try. Thanks to all who have tested LLVM! -Tanya P.S. Documentation review should still be completed today! Thanks! > I've uploaded the 2.0 pre-release to this

> On Tue, May 15, 2007 at 01:23:32AM -0700, Tanya M. Lattner wrote: >> 4) Compile llvm-gcc4 and llvm from source. Run 'make check' and do a 'make >> ENABLE_OPTIMIZED=1 TEST=nightly report' in llvm-test. >> >> It would also be helpful for someone to compile/test with objdir != srcdir. > > This is on FreeBSD 6.2-RELEASE, on i386. > Both llvm and

Hello Xerxes, > llvm 2.9rc1 test on Dualcore ARM running Ubuntu Natty What is the gcc used for the compilation? Can you try to do the -O0 build and see whether this changed the stuff? -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University

Aaron, On Thu, 2007-05-17 at 22:54 +0100, Aaron Gray wrote: > Tanya, > > I have done make check and nightly report tests on LLVM on the GCC 4.2.0 > release, on Linux x86 32 bit. > > On make check the bit intrinsics test is still failing but it works from the > command line, strange ? Can you be a bit more specific about which test is failing? Reid. > > What