Do the buildbots only build debug components? I am seeing lots of this on
trunk with release-style builds:
[x86_64-off-opt]: Failed with signal(SIGABRT) at line 1
[x86_64-off-opt]: while running: llvm-as < /ptmp/dag/llvm-
project.official/llvm/tags/RELEASE_25/test/Transforms/TailDup/basictest2.ll |
opt -tailduplicate -disable-output
[x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name =
'poscnt.1'
[x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name =
'tmp.289'
[x86_64-off-opt]: llvm-as: /ptmp/dag/llvm-
project.official/llvm/tags/RELEASE_25/lib/VMCore/ValueSymbolTable.cpp:29:
llvm::ValueSymbolTable::~ValueSymbolTable(): Assertion `vmap.empty() &&
"Values remain in symbol table!"' failed.
[x86_64-off-opt]: 0 llvm-as 0x000000000056812a
[x86_64-off-opt]: 1 libc.so.6 0x00002af9d6424c10
[x86_64-off-opt]: 2 libc.so.6 0x00002af9d6424b95 gsignal + 53
[x86_64-off-opt]: 3 libc.so.6 0x00002af9d6425f90 abort + 272
[x86_64-off-opt]: 4 libc.so.6 0x00002af9d641e256 __assert_fail + 246
[x86_64-off-opt]: 5 llvm-as 0x00000000004f84f2
[x86_64-off-opt]: 6 llvm-as 0x00000000004b973e llvm::Function::~Function()
+ 238
[x86_64-off-opt]: 7 llvm-as 0x00000000004e3b7f llvm::Module::~Module() +
287
[x86_64-off-opt]: 8 llvm-as 0x000000000044af07 main + 1319
[x86_64-off-opt]: 9 libc.so.6 0x00002af9d6412154 __libc_start_main + 244
[x86_64-off-opt]: 10 llvm-as 0x000000000044a1a9 __gxx_personality_v0 + 169
-Dave
No, some build release, and some build release-asserts. Historically, this is a typical sign of llvm being miscompiled, see the broken-gcc list. - Daniel On Mon, Feb 15, 2010 at 10:09 AM, David Greene <dag at cray.com> wrote:> Do the buildbots only build debug components? I am seeing lots of this on > trunk with release-style builds: > > [x86_64-off-opt]: Failed with signal(SIGABRT) at line 1 > [x86_64-off-opt]: while running: llvm-as < /ptmp/dag/llvm- > project.official/llvm/tags/RELEASE_25/test/Transforms/TailDup/basictest2.ll | > opt -tailduplicate -disable-output > [x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'poscnt.1' > [x86_64-off-opt]: Value still in symbol table! Type = 'i64' Name = 'tmp.289' > [x86_64-off-opt]: llvm-as: /ptmp/dag/llvm- > project.official/llvm/tags/RELEASE_25/lib/VMCore/ValueSymbolTable.cpp:29: > llvm::ValueSymbolTable::~ValueSymbolTable(): Assertion `vmap.empty() && > "Values remain in symbol table!"' failed. > [x86_64-off-opt]: 0 llvm-as 0x000000000056812a > [x86_64-off-opt]: 1 libc.so.6 0x00002af9d6424c10 > [x86_64-off-opt]: 2 libc.so.6 0x00002af9d6424b95 gsignal + 53 > [x86_64-off-opt]: 3 libc.so.6 0x00002af9d6425f90 abort + 272 > [x86_64-off-opt]: 4 libc.so.6 0x00002af9d641e256 __assert_fail + 246 > [x86_64-off-opt]: 5 llvm-as 0x00000000004f84f2 > [x86_64-off-opt]: 6 llvm-as 0x00000000004b973e llvm::Function::~Function() > + 238 > [x86_64-off-opt]: 7 llvm-as 0x00000000004e3b7f llvm::Module::~Module() + > 287 > [x86_64-off-opt]: 8 llvm-as 0x000000000044af07 main + 1319 > [x86_64-off-opt]: 9 libc.so.6 0x00002af9d6412154 __libc_start_main + 244 > [x86_64-off-opt]: 10 llvm-as 0x000000000044a1a9 __gxx_personality_v0 + 169 > > -Dave > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev >
On Monday 15 February 2010 12:16:21 Daniel Dunbar wrote:> No, some build release, and some build release-asserts. > > Historically, this is a typical sign of llvm being miscompiled, see > the broken-gcc list.Yep, that's it. We've been happily using gcc 4.1.2 on OpenSUSE for test builds for some time without problem (we don't use it for releases yet, and won't now!). I guess something changed to make the issue visible to us. BTW, how sure are we that all these are gcc issues and not some incorrect code somewhere that triggers undefined behavior? -Dave