3.7.1 rc2 / 38.0 rc1 - GNU/Linux: CodeGen/asan-globals.cpp fails on i386

[Quuxplusone]

Bugzilla Link	PR25711
Status	NEW
Importance	P normal
Reported by	Sylvestre Ledru (sylvestre@debian.org)
Reported on	2015-12-02 10:14:08 -0800
Last modified on	2018-06-14 18:33:52 -0700
Version	3.7
Hardware	PC Linux
CC	kcc@google.com, llvm-bugs@lists.llvm.org, tstellar@redhat.com, vitalybuka@google.com
Fixed by commit(s)
Attachments	foo.log (11215 bytes, text/x-log)
Blocks
Blocked by
See also

******************** TEST 'Clang :: CodeGen/asan-globals.cpp' FAILED
********************
Script:
--
echo "int extra_global;" > /«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-
llvm/tools/clang/test/CodeGen/Output/asan-globals.cpp.tmp.extra-source.cpp
echo "global:*blacklisted_global*" > /«BUILDDIR»/llvm-toolchain-3.7-
3.7.1~+rc2/build-llvm/tools/clang/test/CodeGen/Output/asan-globals.cpp.tmp.blacklist
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-llvm/Release/bin/clang -cc1 -
internal-isystem /«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-
llvm/Release/bin/../lib/clang/3.7.1/include -nostdsysteminc -include
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-
llvm/tools/clang/test/CodeGen/Output/asan-globals.cpp.tmp.extra-source.cpp -
fsanitize=address -fsanitize-blacklist=/«BUILDDIR»/llvm-toolchain-3.7-
3.7.1~+rc2/build-llvm/tools/clang/test/CodeGen/Output/asan-
globals.cpp.tmp.blacklist -emit-llvm -o -
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/clang/test/CodeGen/asan-globals.cpp |
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-llvm/Release/bin/FileCheck
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/clang/test/CodeGen/asan-globals.cpp
echo "src:/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/clang/test/CodeGen/asan-
globals.cpp" > /«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-
llvm/tools/clang/test/CodeGen/Output/asan-globals.cpp.tmp.blacklist-src
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-llvm/Release/bin/clang -cc1 -
internal-isystem /«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-
llvm/Release/bin/../lib/clang/3.7.1/include -nostdsysteminc -include
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-
llvm/tools/clang/test/CodeGen/Output/asan-globals.cpp.tmp.extra-source.cpp -
fsanitize=address -fsanitize-blacklist=/«BUILDDIR»/llvm-toolchain-3.7-
3.7.1~+rc2/build-llvm/tools/clang/test/CodeGen/Output/asan-
globals.cpp.tmp.blacklist-src -emit-llvm -o -
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/clang/test/CodeGen/asan-globals.cpp |
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/build-llvm/Release/bin/FileCheck
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/clang/test/CodeGen/asan-globals.cpp --
check-prefix=BLACKLIST-SRC
--
Exit Code: 1

Command Output (stderr):
--
/«BUILDDIR»/llvm-toolchain-3.7-3.7.1~+rc2/clang/test/CodeGen/asan-
globals.cpp:33:19: error: expected string not found in input
// BLACKLIST-SRC: ![[GLOBAL]] = !{{{.*}} null, null, i1 false, i1 true}
                  ^
<stdin>:206:1: note: scanning from here
!2 = !{i32* getelementptr inbounds ({ i32, [60 x i8] }, { i32, [60 x i8] }*
@global, i32 0, i32 0), !3, !"global", i1 false, i1 false}
^
<stdin>:206:1: note: with variable "GLOBAL" equal to "2"
!2 = !{i32* getelementptr inbounds ({ i32, [60 x i8] }, { i32, [60 x i8] }*
@global, i32 0, i32 0), !3, !"global", i1 false, i1 false}
^
<stdin>:206:97: note: possible intended match here
!2 = !{i32* getelementptr inbounds ({ i32, [60 x i8] }, { i32, [60 x i8] }*
@global, i32 0, i32 0), !3, !"global", i1 false, i1 false}
                                                                                                ^

--

[Quuxplusone]

How exactly do I reproduce it?

I've tried the following:
- On an x86_64 Ubuntu 14.04
- cmake -DCMAKE_BUILD_TYPE=Release -G Ninja $HOME/llvm -DLLVM_BUILD_32_BITS=1
- ninja check-clang
<passes>

[Quuxplusone]

(In reply to comment #1)
> How exactly do I reproduce it?
>
> I've tried the following:
> - On an x86_64 Ubuntu 14.04
> - cmake -DCMAKE_BUILD_TYPE=Release -G Ninja $HOME/llvm -DLLVM_BUILD_32_BITS=1
> - ninja check-clang
> <passes>

I was also unable to reproduce this on debian stable 32-bit OS (with a 64-bit
CPU).  Sylvestre are you running on i386 HW?

[Quuxplusone]

Also, do you think you could get the full output from the clang command.
you can fust cut and paste the commands output by this test to execute them.

[Quuxplusone]

Attached foo.log (11215 bytes, text/x-log): Full output

[Quuxplusone]

Is this still reproducible?