[llvm-dev] [LLD] [WASM] wasm/function-index.test failing (original) (raw)

Heejin Ahn via llvm-dev llvm-dev at lists.llvm.org
Mon Jan 7 17:02:29 PST 2019

Hello David,

I use x86_64 and it works on my machine. I also can't find this error on LLVM buildbot page. I'd appreciate if you help me reproduce the problem. I tested with debug/release/expensive-check builds and they all passed. Does anyone else have this problem?

Regards, Heejin

On Mon, Jan 7, 2019 at 10:11 AM David Greene via llvm-dev < llvm-dev at lists.llvm.org> wrote:

I'm seeing the following fail on Linux x86-64, for the last couple weeks at least. This is from 'ninja check-all'.

-David FAIL: lld :: wasm/function-index.test (1941 of 1955) ******************** TEST 'lld :: wasm/function-index.test' FAILED ******************** Script: -- : 'RUN: at line 1'; /build/x8664/bin/llc -filetype=obj /src/lld/test/wasm/Inputs/ret32.ll -o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret32.o : 'RUN: at line 2'; /build/x8664/bin/llc -filetype=obj /src/lld/test/wasm/Inputs/ret64.ll -o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret64.o : 'RUN: at line 3'; /build/x8664/bin/wasm-ld -r -o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.wasm /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret32.o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret64.o : 'RUN: at line 4'; /build/x8664/bin/obj2yaml /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.wasm | /build/x8664/bin/FileCheck /src/lld/test/wasm/function-index.test -- Exit Code: 139 Command Output (stderr): -- + : 'RUN: at line 1' + /build/x8664/bin/llc -filetype=obj /src/lld/test/wasm/Inputs/ret32.ll -o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret32.o + : 'RUN: at line 2' + /build/x8664/bin/llc -filetype=obj /src/lld/test/wasm/Inputs/ret64.ll -o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret64.o + : 'RUN: at line 3' + /build/x8664/bin/wasm-ld -r -o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.wasm /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret32.o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret64.o Stack dump: 0. Program arguments: /build/x8664/bin/wasm-ld -r -o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.wasm /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret32.o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret64.o #0 0x0000000000571d1a llvm::sys::PrintStackTrace(llvm::rawostream&) (/build/x8664/bin/wasm-ld+0x571d1a) #1 0x000000000056f538 llvm::sys::RunSignalHandlers() (/build/x8664/bin/wasm-ld+0x56f538) #2 0x000000000056f64c SignalHandler(int) (/build/x8664/bin/wasm-ld+0x56f64c) _#3 0x00007f7578656b00 restorert (/lib64/libpthread.so.0+0x10b00) #4 0x00000000005b618b llvm::SpecificBumpPtrAllocator<std::uniqueptr<llvm::MemoryBuffer,_ _std::defaultdeletellvm::MemoryBuffer > >::DestroyAll() (/build/x8664/bin/wasm-ld+0x5b618b) #5 0x000000000091af30 lld::freeArena() (/build/x8664/bin/wasm-ld+0x91af30) #6 0x00000000007b9e5c lld::wasm::link(llvm::ArrayRef<char const*>, bool, llvm::rawostream&) (/build/x8664/bin/wasm-ld+0x7b9e5c) #7 0x00000000004a67cf main (/build/x8664/bin/wasm-ld+0x4a67cf) _#8 0x00007f7576e656e5 libcstartmain (/lib64/libc.so.6+0x206e5) #9 0x0000000000557729 start /home/abuild/rpmbuild/BUILD/glibc-2.22/csu/../sysdeps/x8664/start.S:121:0 /build/x8664/tools/lld/test/wasm/Output/function-index.test.script: line 4: 368695 Segmentation fault /build/x8664/bin/wasm-ld -r -o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.wasm /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret32.o /build/x8664/tools/lld/test/wasm/Output/function-index.test.tmp.ret64.o -David

LLVM Developers mailing list llvm-dev at lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20190107/cf5e1bb6/attachment.html>

More information about the llvm-dev mailing list