"Tanya M. Lattner" <tonic at nondot.org> writes: Tanya, There is no reason to include the CMake build system on this release. It is undocumented and immature. Please remove the cmake/ directory and all files named CMakeLists.txt from the LLVM source tree. -- Oscar
LLVMers,
The 2.4 pre-release (v2) is available for testing:
http://llvm.org/prereleases/2.4/
If you have time, I'd appreciate anyone who can help test the release.
Please do the following:
1) Download/compile llvm source, and either compile llvm-gcc source or use
llvm-gcc binary.
2) Run make check, send me the testrun.log
3) Run "make TEST=nightly report" and send me the report.nightly.txt
4) Please provide details on what platform you compiled LLVM on and how
you built LLMV (src == obj, or src != obj)
Please COMPLETE ALL TESTING BY the end of the day on November 5th.
Thanks,
Tanya
P.S. PPC llvm-gcc binary will be up later today. Sorry for the delay.
On Oct 31, 2008, at 2:04 PM, Óscar Fuentes wrote:> "Tanya M. Lattner" <tonic at nondot.org> writes: > > Tanya, > > There is no reason to include the CMake build system on this > release. It > is undocumented and immature. > > Please remove the cmake/ directory and all files named CMakeLists.txt > from the LLVM source tree.If there is no harm of including it, I'd prefer to just leave it in. We don't want to have to respin builds unless absolutely necessary, -Chris
Tanya M. Lattner dixit:>LLVMers, > >The 2.4 pre-release (v2) is available for testing: >http://llvm.org/prereleases/2.4/Is it correct that there is no matching clang distfile? A checkout of clang r58548 does not build with the prerelease, seems to require a newer version of llvm-current. (But then, maybe it’d be best anyway if I port llvm-current to MirBSD, because it’ll be easier for you to merge the diffs back in.) bye, //mirabilos -- Sometimes they [people] care too much: pretty printers [and syntax highligh- ting, d.A.] mechanically produce pretty output that accentuates irrelevant detail in the program, which is as sensible as putting all the prepositions in English text in bold font. -- Rob Pike in "Notes on Programming in C"
Dixi quod…>A checkout of clang r58548 does not build with the prerelease, >seems to require a newer version of llvm-current.However, clang r58565 does not build with llvm r58565 either: llvm[4]: Compiling BasicConstraintManager.cpp for Release-Asserts build mpcxx -I/usr/ports/lang/llvm/w-llvm-58565-0/llvm/include -I/usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis -DNDEBUG -I/usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis/../../include -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -O3 -fno-exceptions -fno-rtti -Woverloaded-virtual -pedantic -Wall -W -Wwrite-strings -Wno-long-long -Wunused -Wno-unused-parameter -c BasicConstraintManager.cpp -o /usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis/Release-Asserts/BasicConstraintManager.o In file included from /usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis/../../include/clang/Analysis/PathSensitive/Store.h:18, from /usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis/../../include/clang/Analysis/PathSensitive/ConstraintManager.h:18, from BasicConstraintManager.cpp:15: /usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis/../../include/clang/Analysis/PathSensitive/MemRegion.h:246: error: base `clang::AnonTypedRegion' with only non-default constructor in class without a constructor gmake[4]: *** [/usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis/Release-Asserts/BasicConstraintManager.o] Error 1 gmake[4]: Leaving directory `/usr/ports/lang/llvm/w-llvm-58565-0/llvm/tools/clang/lib/Analysis' Any suggestions? bye, //mirabilos -- "Using Lynx is like wearing a really good pair of shades: cuts out the glare and harmful UV (ultra-vanity), and you feel so-o-o COOL." -- Henry Nelson, March 1999
On Nov 2, 2008, at 6:55 AM, Thorsten Glaser wrote:> Tanya M. Lattner dixit: > >> LLVMers, >> >> The 2.4 pre-release (v2) is available for testing: >> http://llvm.org/prereleases/2.4/ > > Is it correct that there is no matching clang distfile? > A checkout of clang r58548 does not build with the prerelease, > seems to require a newer version of llvm-current. >clang is not yet a part of the normal LLVM release process. Once its ready, we will incorporate it into the release process. For now, if you want to use clang, you need to use LLVM svn TOT. -Tanya> (But then, maybe it’d be best anyway if I port llvm-current to > MirBSD, because it’ll be easier for you to merge the diffs back in.) > > bye, > //mirabilos > -- > Sometimes they [people] care too much: pretty printers [and syntax > highligh- > ting, d.A.] mechanically produce pretty output that accentuates > irrelevant > detail in the program, which is as sensible as putting all the > prepositions > in English text in bold font. -- Rob Pike in "Notes on Programming > in C" > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Hi, I've just tried out version 2.4, and it doesn't work for me in
situations where 2.3 seems fine. The current trunk code appears to have
the same problem.
When I compile a simple program in llvm-gcc, I get a .bc file as output
as expected. When running lli or llc on this file, however, I get
various errors and an assert, stopping the .s file from being created.
Example output of llc:
[bens at BenSCentOS llvm]$ llc hello.bc -o hello.s
Value still in symbol table! Type = 'i32' Name = 'tmp3.3'
Value still in symbol table! Type = 'i32' Name = 'tmp3.4'
Value still in symbol table! Type = 'i32' Name = 'tmp1'
Value still in symbol table! Type = 'i32' Name = 'tmp3'
Value still in symbol table! Type = 'i32' Name = 'tmp3.1'
Value still in symbol table! Type = 'i32' Name = 'tmp3.2'
llc: ValueSymbolTable.cpp:29:
llvm::ValueSymbolTable::~ValueSymbolTable(): Assertion `vmap.empty() &&
"Values remain in symbol table!"' failed.
llc[0x89482d6]
/lib/libc.so.6(abort+0x101)[0xc7a631]
/lib/libc.so.6(__assert_fail+0xfb)[0xc7216b]
llc[0x88e92ba]
Aborted
When I run lli, I get pretty much the same, except that the program's
expected output appears before all the errors (so I guess it is doing
some good in there, looks like something just isn't tidying itself up
afterwards).
Opening hello.bc as-is in an editor shows that there is some data in
there (about the same amount as I had when compiling with 2.3), but when
I run llvm-dis on it, it outputs blank.
I ran the llvm/configure file with the same options as I did for 2.3
(--enable-optimized, that's it)
I'm building with a Linux machine,
CentOS 5
Dual core Pentium 4, 3.2GHz x 2
1GB RAM
Am I somehow getting something wrong, or is 2.4 broken? The problem
isn't with my test program, I've tried it with a few c files of varying
simplicity.
Ben
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
On Behalf Of Tanya M. Lattner
Sent: 31 October 2008 21:07
To: LLVM Developers Mailing List
Subject: [LLVMdev] 2.4 Pre-release (v2)
LLVMers,
The 2.4 pre-release (v2) is available for testing:
http://llvm.org/prereleases/2.4/
If you have time, I'd appreciate anyone who can help test the release.
Please do the following:
1) Download/compile llvm source, and either compile llvm-gcc source or
use
llvm-gcc binary.
2) Run make check, send me the testrun.log
3) Run "make TEST=nightly report" and send me the report.nightly.txt
4) Please provide details on what platform you compiled LLVM on and how
you built LLMV (src == obj, or src != obj)
Please COMPLETE ALL TESTING BY the end of the day on November 5th.
Thanks,
Tanya
P.S. PPC llvm-gcc binary will be up later today. Sorry for the delay.
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
Hi, Ben> Hi, I've just tried out version 2.4, and it doesn't work for me in > situations where 2.3 seems fine. The current trunk code appears to have > the same problem. > Value still in symbol table! Type = 'i32' Name = 'tmp3.3'It seems, that you're using gcc, which is known to be broken http://llvm.org/docs/GettingStarted.html#brokengcc -- With best regards, Anton Korobeynikov Faculty of Mathematics and Mechanics, Saint Petersburg State University