[llvm-bugs] [Bug 43179] Assertion failure in CastValueChecker: ArrayRef indexed out of bounds
https://bugs.llvm.org/show_bug.cgi?id=43179 Artem Dergachev changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #2 from Artem Dergachev --- Fixed in r371256. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43248] New: [GNU C extension] support `asm inline`
https://bugs.llvm.org/show_bug.cgi?id=43248 Bug ID: 43248 Summary: [GNU C extension] support `asm inline` Product: clang Version: 9.0 Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: ndesaulni...@google.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk Looks like GCC 8.3 added support for `asm inline`. Seems to be another qualifier like `asm volatile` but instead the cost model assumes the size is [near-]zero(?). https://godbolt.org/z/w3_mc8 https://github.com/gcc-mirror/gcc/commit/6de46ad5326fc5e6b730a2feb8c62d09c1561f92 Which looks like the qualifier was added to this page: https://gcc.gnu.org/onlinedocs/gcc/Extended-Asm.html -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 32146] Enable -verify-machineinstrs with EXPENSIVE_CHECKS
https://bugs.llvm.org/show_bug.cgi?id=32146 Bug 32146 depends on bug 27481, which changed state. Bug 27481 Summary: X86 make check has a bunch of machine verifier errors https://bugs.llvm.org/show_bug.cgi?id=27481 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 27481] X86 make check has a bunch of machine verifier errors
https://bugs.llvm.org/show_bug.cgi?id=27481 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #38 from Reid Kleckner --- (In reply to Francis Visoiu Mistrih from comment #37) > Thanks! > > * Clang fix: r345591 > * LLVM fix + re-enable: r345593 Marking fixed. Separately, I was wondering if maybe the machine verifier should be enabled somehow in +asserts builds, or controlled by some llc flag that's always set when lit calls llc, so that we get earlier detection of issues. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43247] New: Long live ranges of constants don't get rematerialized
https://bugs.llvm.org/show_bug.cgi?id=43247 Bug ID: 43247 Summary: Long live ranges of constants don't get rematerialized Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Register Allocator Assignee: unassignedb...@nondot.org Reporter: aemer...@apple.com CC: llvm-bugs@lists.llvm.org, quentin.colom...@gmail.com We're enabling the localizer pass for optimizations in AArch64 GlobalISel, which is a pass that tries to duplicate and move defs of constant-like instructions close to their uses, so as to reduce the live ranges and register pressure. It would be good if the greedy register allocator could handle this problem for us, but it seems to have been written with only SelectionDAG in mind which is always block-local and doesn't have any notion of live range in its graph representation. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43246] New: [InstSimplify] Failure to drop check-for-zero after uadd_with_overflow
https://bugs.llvm.org/show_bug.cgi?id=43246
Bug ID: 43246
Summary: [InstSimplify] Failure to drop check-for-zero after
uadd_with_overflow
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: lebedev...@gmail.com
CC: llvm-bugs@lists.llvm.org
https://rise4fun.com/Alive/yFB
Name: zz
Pre: C != 0
%1 = add i64 C, %offset
%2 = icmp ne i64 %1, 0
%3 = icmp uge i64 %1, C
%r = and i1 %2, %3
=>
%r = icmp uge i64 %1, C
This comes up in https://reviews.llvm.org/D67122
for the code like
char* test(char& base, unsigned long offset) {
return + offset;
}
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43245] New: llvm-readelf --stack-sizes does not report all functions that share code
https://bugs.llvm.org/show_bug.cgi?id=43245
Bug ID: 43245
Summary: llvm-readelf --stack-sizes does not report all
functions that share code
Product: tools
Version: trunk
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: llvm-readobj
Assignee: unassignedb...@nondot.org
Reporter: wolfgang_p...@playstation.sony.com
CC: jh7370.2...@my.bristol.ac.uk, llvm-bugs@lists.llvm.org
// Given the following C source:
static void bash ()
{}
static void bash1 ()
{}
int main ()
{
bash ();
bash1 ();
return 0;
}
// end
When compiled with --function-sections -fstack-size-section and linked with lld
--gc-sections -icf=all, bash() and bash1() are physically represented by the
same code and the symbols for both functions have the same value.
llvm-readelf --stack-sizes, when invoked on the executable, displays only the
stack size for one of the functions.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 42012] IfConverter asserting on INLINEASM_BR MachineInstr
https://bugs.llvm.org/show_bug.cgi?id=42012 Nick Desaulniers changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Nick Desaulniers --- Reopening; r37 may have fixed the IR from D62555, but the larger issue is still a problem. I spoke too soon: https://github.com/ClangBuiltLinux/linux/issues/494#issuecomment-528952495 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 4068] [Meta] Compiling the Linux kernel with clang
https://bugs.llvm.org/show_bug.cgi?id=4068 Bug 4068 depends on bug 42012, which changed state. Bug 42012 Summary: IfConverter asserting on INLINEASM_BR MachineInstr https://bugs.llvm.org/show_bug.cgi?id=42012 What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43184] LLVM :: Reduce/remove tests not finding python on Ubuntu 18.04
https://bugs.llvm.org/show_bug.cgi?id=43184 Luke changed: What|Removed |Added Status|NEW |RESOLVED CC||dblai...@gmail.com Resolution|--- |FIXED --- Comment #2 from Luke --- Fixed by r371143 Use %python from lit to get the correct/valid python bin Thanks David! -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 37195] llvm/lib/ExecutionEngine/RuntimeDyld/Targets/RuntimeDyldMachOARM.h:208: possible typo ?
https://bugs.llvm.org/show_bug.cgi?id=37195 Simon Pilgrim changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED CC||llvm-...@redking.me.uk --- Comment #1 from Simon Pilgrim --- *** This bug has been marked as a duplicate of bug 42036 *** -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 34465] llvm/tools/clang/lib/StaticAnalyzer/Core/CallEvent.cpp:100: dead code ?
https://bugs.llvm.org/show_bug.cgi?id=34465 Simon Pilgrim changed: What|Removed |Added CC||llvm-...@redking.me.uk Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from Simon Pilgrim --- *** This bug has been marked as a duplicate of bug 34467 *** -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43241] Regression(370635): " section '.text' cannot be removed because it is referenced by the section '.ARM.exidx'" when using llvm-objcopy --extract-partition
https://bugs.llvm.org/show_bug.cgi?id=43241 Fangrui Song changed: What|Removed |Added CC||i...@maskray.me Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Fangrui Song --- Fixed by r371216 partitions + --icf=all + .ARM.exidx (sh_link pointing to .text) This is an under-tested area... -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43244] New: 9.0rc3 SingleSource/UnitTests/Vector/AVX512F/Vector-AVX512F-t_movzext.test fails
https://bugs.llvm.org/show_bug.cgi?id=43244 Bug ID: 43244 Summary: 9.0rc3 SingleSource/UnitTests/Vector/AVX512F/Vector-AVX512F-t _movzext.test fails Product: clang Version: 9.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: brian.c...@gmail.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk While running the test-release.sh on Ubuntu 16.04, the test-suite run fails on 'SingleSource/UnitTests/Vector/AVX512F/Vector-AVX512F-t_movzext.test'. The build machine I used has a skylake CPU (Silver 4114). My previous builds of llvm+clang on Ubuntu 16 were usually on a much older AMD CPU that would have not had support for this AVX512 test case. Because of the test's description and the failure mode, I've speculated that this is a codegen failure. ~~~ FAIL: test-suite :: SingleSource/UnitTests/Vector/AVX512F/Vector-AVX512F-t_movzext.test (930 of 991) TEST 'test-suite :: SingleSource/UnitTests/Vector/AVX512F/Vector-AVX512F-t_movzext.test' FAILED /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/tools/timeit-target --limit-core 0 --limit-cpu 7200 --timeout 7200 --limit-file-size 104857600 --limit-rss-size 838860800 --append-exitstatus --redirect-output /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/SingleSource/UnitTests/Vector/AVX512F/Output/Vector-AVX512F-t_movzext.test.out --redirect-input /dev/null --chdir /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/SingleSource/UnitTests/Vector/AVX512F --summary /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/SingleSource/UnitTests/Vector/AVX512F/Output/Vector-AVX512F-t_movzext.test.time /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/SingleSource/UnitTests/Vector/AVX512F/Vector-AVX512F-t_movzext cd /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/SingleSource/UnitTests/Vector/AVX512F ; /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/tools/fpcmp-target /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/SingleSource/UnitTests/Vector/AVX512F/Output/Vector-AVX512F-t_movzext.test.out t_movzext.reference_output /local/mnt/brian/bcain_clang_tedwood-ubuntu_9506/llvm/utils/release/rc3/test-suite-build/tools/fpcmp-target: files differ without tolerance allowance Testing: 0 .. 10.. 20.. 30.. 40.. 50.. 60.. 70.. 80.. 90.. Testing Time: 82.47s Failing Tests (1): test-suite :: SingleSource/UnitTests/Vector/AVX512F/Vector-AVX512F-t_movzext.test Expected Passes: 990 Unexpected Failures: 1 CMakeFiles/check.dir/build.make:1047: recipe for target 'CMakeFiles/check' failed -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43243] New: clang-9 fails to drop static symbols with an alias
https://bugs.llvm.org/show_bug.cgi?id=43243
Bug ID: 43243
Summary: clang-9 fails to drop static symbols with an alias
Product: clang
Version: 9.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: a...@linaro.org
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
A linux kernel randconfig build resulted in a link error from duplicated
symbols that were declared static:
drivers/pinctrl/aspeed/pinctrl-aspeed-g6.o:(.data+0x10): multiple definition of
`sig_exprs_0_GPIOA0'
drivers/pinctrl/aspeed/pinctrl-aspeed-g4.o:(.data+0x8): first defined here
drivers/pinctrl/aspeed/pinctrl-aspeed-g6.o:(.data+0x28): multiple definition of
`sig_exprs_1_GPIOA1'
drivers/pinctrl/aspeed/pinctrl-aspeed-g4.o:(.data+0x18): first defined here
drivers/pinctrl/aspeed/pinctrl-aspeed-g6.o:(.data+0x40): multiple definition of
`sig_exprs_2_GPIOA2'
drivers/pinctrl/aspeed/pinctrl-aspeed-g4.o:(.data+0x28): first defined here
...
I reduced this to a trivial test case:
https://godbolt.org/z/Azn8pH
$ cat pinctrl-aspeed-g6.i
static const int sig_exprs_SCL11_I2C11[] = {};
static const int sig_exprs_0_SCL11
__attribute__((alias("sig_exprs_SCL11_I2C11")));
$ clang-9 -Wall -O2 -c pinctrl-aspeed-g6.i
$ objdump --syms pinctrl-aspeed-g6.o
pinctrl-aspeed-g6.o: file format elf64-x86-64
SYMBOL TABLE:
ldf *ABS* pinctrl-aspeed-g6.i
g O .rodata sig_exprs_0_SCL11
With clang-10, this problem is fixed:
$ clang-10 -Wall -O2 -c pinctrl-aspeed-g6.i
$ objdump --syms pinctrl-aspeed-g6.o
pinctrl-aspeed-g6.o: file format elf64-x86-64
SYMBOL TABLE:
ldf *ABS* pinctrl-aspeed-g6.i
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 10075 in oss-fuzz: llvm/clang-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #7 on issue 10075 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "E https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10075#c7 ClusterFuzz testcase 5102081510211584 is verified as fixed in https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201909020324:201909060434 If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43242] New: Regression: clang crashes when processing operator() call in a lambda
https://bugs.llvm.org/show_bug.cgi?id=43242
Bug ID: 43242
Summary: Regression: clang crashes when processing operator()
call in a lambda
Product: clang
Version: trunk
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: C++11
Assignee: unassignedclangb...@nondot.org
Reporter: wye...@ca.ibm.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
This started failing some time after SVN change #370966 (it was clean with
370966).
> cat t.cpp
int main() {
[&](int x){ operator()(); }();
}
> clang++ -std=c++11 -c t.cpp
t.cpp:2:14: error: use of undeclared 'operator()'
[&](int x){ operator()(); }();
^
this->
t.cpp:2:2: note: must qualify identifier to find this declaration in dependent
base class
[&](int x){ operator()(); }();
^
t.cpp:2:14: error: call to non-static member function without an object
argument
[&](int x){ operator()(); }();
^~~~
clang-10: ~/Source/llvm-project/clang/include/clang/AST/Type.h:659: const
clang::ExtQualsTypeCommonBase *clang::QualType::getCommonPtr() const: Assertion
`!isNull() && "Cannot retrieve a
NULL type pointer"' failed.
Stack dump:
0. Program arguments: /home/wyehia/build/bin/clang-10 -cc1 -triple
powerpc64le-unknown-linux-gnu -emit-obj -mrelax-all -disable-free
-main-file-name t.cpp -mrelocation-model static -mthread-model posix
-mframe-pointer=all -fmath-errno -masm-verbose -mconstructor-aliases
-fuse-init-array -target-cpu ppc64le -mfloat-abi hard -target-abi elfv2
-dwarf-column-info -debugger-tuning=gdb -coverage-notes-file /tmp/t.gcno
-resource-dir /home/wyehia/build/lib/clang/10.0.0 -internal-isystem
/usr/lib/gcc/powerpc64le-linux-gnu/7.3.0/../../../../include/c++/7.3.0
-internal-isystem
/usr/lib/gcc/powerpc64le-linux-gnu/7.3.0/../../../../include/powerpc64le-linux-gnu/c++/7.3.0
-internal-isystem
/usr/lib/gcc/powerpc64le-linux-gnu/7.3.0/../../../../include/powerpc64le-linux-gnu/c++/7.3.0
-internal-isystem
/usr/lib/gcc/powerpc64le-linux-gnu/7.3.0/../../../../include/c++/7.3.0/backward
-internal-isystem /home/wyehia/build/lib/clang/10.0.0/include/ppc_wrappers
-internal-isystem /usr/local/include -internal-isystem
/home/wyehia/build/lib/clang/10.0.0/include -internal-externc-isystem
/usr/include/powerpc64le-linux-gnu -internal-externc-isystem /include
-internal-externc-isystem /usr/include -std=c++11 -fdeprecated-macro
-fdebug-compilation-dir /tmp -ferror-limit 19 -fmessage-length 0
-fno-signed-char -fobjc-runtime=gcc -fcxx-exceptions -fexceptions
-fdiagnostics-show-option -faddrsig -o t.o -x c++ t.cpp
1. t.cpp:2:29: current parser token '('
2. t.cpp:1:12: parsing function body 'main'
3. t.cpp:1:12: in compound statement ('{}')
4. t.cpp:2:2: lambda expression parsing
#0 0x7caa60c36d04 PrintStackTraceSignalHandler(void*)
(/home/wyehia/build/bin/../lib/libLLVMSupport.so.10svn+0x1d6d04)
#1 0x7caa60c33f38 llvm::sys::RunSignalHandlers()
(/home/wyehia/build/bin/../lib/libLLVMSupport.so.10svn+0x1d3f38)
#2 0x7caa60c37150 SignalHandler(int)
(/home/wyehia/build/bin/../lib/libLLVMSupport.so.10svn+0x1d7150)
#3 0x7caa66c604d8 (linux-vdso64.so.1+0x4d8)
#4 0x7caa5edee98c __libc_signal_restore_set
/build/glibc-uvws04/glibc-2.27/signal/../sysdeps/unix/sysv/linux/nptl-signals.h:80:0
#5 0x7caa5edee98c raise
/build/glibc-uvws04/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:48:0
#6 0x7caa5edf0be0 abort /build/glibc-uvws04/glibc-2.27/stdlib/abort.c:79:0
#7 0x7caa5eddbb38 __assert_fail_base
/build/glibc-uvws04/glibc-2.27/assert/assert.c:92:0
#8 0x7caa5eddbbe4 __assert_fail
/build/glibc-uvws04/glibc-2.27/assert/assert.c:101:0
#9 0x7caa5cb43f6c clang::Sema::BuildCXXThisExpr(clang::SourceLocation,
clang::QualType, bool)
(/home/wyehia/build/bin/../lib/../lib/libclangSema.so.10svn+0x4e3f6c)
#10 0x7caa5cc1841c clang::Sema::BuildCaptureInit(clang::sema::Capture
const&, clang::SourceLocation, bool)
(/home/wyehia/build/bin/../lib/../lib/libclangSema.so.10svn+0x5b841c)
#11 0x7caa5cc18dc8 clang::Sema::BuildLambdaExpr(clang::SourceLocation,
clang::SourceLocation, clang::sema::LambdaScopeInfo*)
(/home/wyehia/build/bin/../lib/../lib/libclangSema.so.10svn+0x5b8dc8)
#12 0x7caa5cc1866c clang::Sema::ActOnLambdaExpr(clang::SourceLocation,
clang::Stmt*, clang::Scope*)
(/home/wyehia/build/bin/../lib/../lib/libclangSema.so.10svn+0x5b866c)
#13 0x7caa5d165944
clang::Parser::ParseLambdaExpressionAfterIntroducer(clang::LambdaIntroducer&)
(/home/wyehia/build/bin/../lib/../lib/libclangParse.so.10svn+0x95944)
#14 0x7caa5d163150 clang::Parser::ParseLambdaExpression()
(/home/wyehia/build/bin/../lib/../lib/libclangParse.so.10svn+0x93150)
#15 0x7caa5d1525e8
[llvm-bugs] [Bug 43241] New: Regression(370635): " section '.text' cannot be removed because it is referenced by the section '.ARM.exidx'" when using llvm-objcopy --extract-partition
https://bugs.llvm.org/show_bug.cgi?id=43241 Bug ID: 43241 Summary: Regression(370635): " section '.text' cannot be removed because it is referenced by the section '.ARM.exidx'" when using llvm-objcopy --extract-partition Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: ELF Assignee: unassignedb...@nondot.org Reporter: nicolaswe...@gmx.de CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org Grab --reproduce output: https://drive.google.com/file/d/1m5fCTdnonSqdznHNrhmhtlnPXIVDk3q8/view?usp=sharing (~600MB gzip) This produces lib.unstripped/libchrome__combined.so which is then fed into llvm-objcopy like so: ` ../../../../llvm-project/out/gn/bin/llvm-objcopy --extract-partition libvr.so lib.unstripped/libchrome__combined.so`. That errors out after r370635: $ ../../../../llvm-project/out/gn/bin/llvm-objcopy --extract-partition libvr.so lib.unstripped/libchrome__combined.so ../../../../llvm-project/out/gn/bin/llvm-objcopy: error: 'lib.unstripped/libchrome__combined.so': section '.text' cannot be removed because it is referenced by the section '.ARM.exidx' (Originally at https://crbug.com/1000647) -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43240] New: KNL: inline memcpy uses two ymm loads/stores instead of one zmm load/store
https://bugs.llvm.org/show_bug.cgi?id=43240
Bug ID: 43240
Summary: KNL: inline memcpy uses two ymm loads/stores instead
of one zmm load/store
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: X86
Assignee: unassignedb...@nondot.org
Reporter: d...@znu.io
CC: craig.top...@gmail.com, llvm-bugs@lists.llvm.org,
llvm-...@redking.me.uk, spatel+l...@rotateright.com
The following code generates two ymm loads/stores instead of a single zmm
load/store. This seems specific to knl because skylake-avx512 and
icelake-client both generate the correct code. And yes, this example is derived
from test/CodeGen/X86/memcpy.ll.
declare void @llvm.memcpy.p0i8.p0i8.i64(i8* nocapture, i8* nocapture, i64, i1)
nounwind
define void @test(i8* nocapture %A, i8* nocapture %B) nounwind optsize
noredzone {
entry:
tail call void @llvm.memcpy.p0i8.p0i8.i64(i8* %A, i8* %B, i64 64, i1 false)
ret void
}
Expected result (as seen with skylake-avx512 and icelake-client):
vmovups (%rsi), %zmm0
vmovups %zmm0, (%rdi)
retq
Actual result (as seen with knl):
vmovups (%rsi), %ymm0
vmovups 32(%rsi), %ymm1
vmovups %ymm1, 32(%rdi)
vmovups %ymm0, (%rdi)
retq
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43239] New: Missed optimization: extra XOR and FMA
https://bugs.llvm.org/show_bug.cgi?id=43239
Bug ID: 43239
Summary: Missed optimization: extra XOR and FMA
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: zamazan...@tut.by
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
For the code below:
#include
double t1(double x, double y)
{
return std::sqrt(x*x + y*y);
}
clang(trunk) with '-O3 -ffast-math' generates:
t1(double, double):# @t1(double, double)
mulsd xmm0, xmm0
mulsd xmm1, xmm1
addsd xmm1, xmm0
xorps xmm0, xmm0
sqrtsd xmm0, xmm1
ret
gcc(trunk) with '-O3 -ffast-math' is better here (doesn't add extra xorps
instr) and generates:
t1(double, double):
mulsd xmm1, xmm1
mulsd xmm0, xmm0
addsd xmm0, xmm1
sqrtsd xmm0, xmm0
ret
Godbolt playground: https://godbolt.org/z/Cx9EDI
Also note that with '-O3 -march=native -ffast-math' both compilers (gcc(trunk)
and clang(trunk)) generate equal code:
t1(double, double):
vmulsd xmm1, xmm1, xmm1
vfmadd132sd xmm0, xmm1, xmm0
vsqrtsd xmm0, xmm0, xmm0
ret
Godbolt playground: https://godbolt.org/z/fHgGxw
But without '-ffast-math' outputs are different: clang doesn't use FMA instr.
Godbolt playground: https://godbolt.org/z/X46_hD
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40785] Print unknown st_other value if present in GNU output
https://bugs.llvm.org/show_bug.cgi?id=40785 George Rimar changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #10 from George Rimar --- r371201 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43238] New: Integer promotion quirk prevents efficient power of 2 division
https://bugs.llvm.org/show_bug.cgi?id=43238
Bug ID: 43238
Summary: Integer promotion quirk prevents efficient power of 2
division
Product: clang
Version: 8.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: LLVM Codegen
Assignee: unassignedclangb...@nondot.org
Reporter: kim.nils...@effnet.com
CC: llvm-bugs@lists.llvm.org, neeil...@live.com,
richard-l...@metafoo.co.uk
Created attachment 22476
--> https://bugs.llvm.org/attachment.cgi?id=22476=edit
Example LLVM IR
For the function,
uint_fast32_t foo_a(uint_fast8_t x) {
const uint_fast32_t q = 1 << x;
return 256 / q;
}
GCC-{8.*,9.*} generates inefficient division instructions for both x86_64 and
ARM. Since 'q' is a power of 2, the result should be a single right shift.
Indeed, if the function is changed to,
uint_fast32_t foo_b(uint_fast8_t x) {
return 256 / (1 << x); // This is, of course, equivalent to (256 >> x)
},
the expected instructions are generated. Counter-intuitively, if the original
function is instead changed slightly to,
uint_fast32_t foo_c(uint_fast8_t x) {
const uint_fast32_t q = (uint_fast32_t)1 << x;
return 256 / q;
},
the expected instructions are once again generated.
See https://godbolt.org/z/X-It3b for examples.
(FWIW, GCC also has this behavior and I've reported the same thing there
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91680)
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43237] New: Indentation of nested scopes is incorrect
https://bugs.llvm.org/show_bug.cgi?id=43237
Bug ID: 43237
Summary: Indentation of nested scopes is incorrect
Product: clang
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Formatter
Assignee: unassignedclangb...@nondot.org
Reporter: jan.vali...@fpt.sk
CC: djas...@google.com, kli...@google.com,
llvm-bugs@lists.llvm.org
Indentation of multiple nested scopes is incorrect. It doesn't matter what are
settings of clang-format. Bad output is produced also with default settings for
all clang-format styles(webkit,llvm,etc...).
Steps to Reproduce:
Create source file with content as:
void fc()
{
// scope1
{
// scope2
{
int a;
}
}
// scope3
{
int b;
}
}
When clang-format is applied actual result is:
void fc()
{
// scope1
{ // scope2
{ int a;
}
}
// scope3
{
int b;
}
}
Expected result(if parameter IndentLength is 4) is:
void fc()
{
// scope1
{
// scope2
{
int a;
}
}
// scope3
{
int b;
}
}
But if scope3 is removed, indentation of scope1/scope2 is correct.
It seems that it behaves same for all versions of clang-format.
(tested on https://zed0.co.uk/clang-format-configurator/)
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43236] Merge lld r369828 and r371013 into 9.0
https://bugs.llvm.org/show_bug.cgi?id=43236 Hans Wennborg changed: What|Removed |Added Blocks||42474 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Hans Wennborg --- Yes, there will be an rc4, so let's take these. Merged in r371196 and r371197, respectively. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=42474 [Bug 42474] [meta] 9.0.0 Release Blockers -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 42474] [meta] 9.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=42474 Bug 42474 depends on bug 43236, which changed state. Bug 43236 Summary: Merge lld r369828 and r371013 into 9.0 https://bugs.llvm.org/show_bug.cgi?id=43236 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 17027 in oss-fuzz: llvm:llvm-dwarfdump-fuzzer: ASSERT: FullLength == length()
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, mit...@google.com, bigchees...@gmail.com, eney...@google.com, llvm-b...@lists.llvm.org, j...@chromium.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-09-06 Type: Bug New issue 17027 by ClusterFuzz-External: llvm:llvm-dwarfdump-fuzzer: ASSERT: FullLength == length() https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17027 Detailed Report: https://oss-fuzz.com/testcase?key=5754702871920640 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: ASSERT Crash Address: Crash State: FullLength == length() llvm::DWARFListTableHeader::extract llvm::DWARFListTableBase::extract Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201909020324:201909060434 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5754702871920640 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43236] New: Merge lld r369828 and r371013 into 9.0
https://bugs.llvm.org/show_bug.cgi?id=43236
Bug ID: 43236
Summary: Merge lld r369828 and r371013 into 9.0
Product: lld
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: ELF
Assignee: unassignedb...@nondot.org
Reporter: dimi...@andric.com
CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org
Please merge https://reviews.llvm.org/rLLD371013 ("Align output segments
correctly") and its prerequisite https://reviews.llvm.org/rLLD369828 ("[ELF]
Align the first section of a PT_LOAD even if its type is SHT_NOBITS") into lld
9.0.
This fixes bug 43212, which was about incorrectly aligned segments when the
--omagic or --nmagic link options were used.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43227] [X86] EltsFromConsecutiveLoads - incorrect folding of non-zero offset base loads
https://bugs.llvm.org/show_bug.cgi?id=43227 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Simon Pilgrim --- Resolving - confirmed fixed -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43235] New: libLLVMObject.so.10svn fails to link error: undefined reference to 'llvm::raw_string_ostream::current_pos() const'
https://bugs.llvm.org/show_bug.cgi?id=43235 Bug ID: 43235 Summary: libLLVMObject.so.10svn fails to link error: undefined reference to 'llvm::raw_string_ostream::current_pos() const' Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Object Assignee: unassignedb...@nondot.org Reporter: m...@fireburn.co.uk CC: llvm-bugs@lists.llvm.org Created attachment 22475 --> https://bugs.llvm.org/attachment.cgi?id=22475=edit Build log xz compressed FAILED: lib/libLLVMObject.so.10svn : && /usr/bin/x86_64-pc-linux-gnu-g++ -m32 -fPIC -O3 -march=native -pipe -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++14 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wng -Wimplicit-fallthrough -Wno-maybe-uninitialized -Wno-class-memaccess -Wno-noexcept-type -Wdelete-non-virtual-dtor -Wno-comment -fdiagnostics-color -ffunction-sections -fdata-sections -Wl,-O1 -Wl,--hclude/ -Wl,-z,defs -Wl,-z,nodelete -Wl,-O3 -Wl,--gc-sections -shared -Wl,-soname,libLLVMObject.so.10svn -o lib/libLLVMObject.so.10svn lib/Object/CMakeFiles/LLVMObject.dir/Archive.cpp.o lib/Object/CMak/CMakeFiles/LLVMObject.dir/Binary.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/COFFImportFile.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/COFFModuleDefinition.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/COFir/Decompressor.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/ELF.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/ELFObjectFile.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/Error.cpp.o lib/Object/CMakeFiles/LLVMOLVMObject.dir/IRSymtab.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/MachOObjectFile.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/MachOUniversal.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/Minidump.cpp.o lib/pp.o lib/Object/CMakeFiles/LLVMObject.dir/Object.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/ObjectFile.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/RecordStreamer.cpp.o lib/Object/CMakeFiles/LLVMObject.diMObject.dir/SymbolicFile.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/SymbolSize.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/TapiFile.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/TapiUniversal.cpp.o lib/Objeb/Object/CMakeFiles/LLVMObject.dir/WindowsMachineFlag.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/WindowsResource.cpp.o lib/Object/CMakeFiles/LLVMObject.dir/XCOFFObjectFile.cpp.o -Wl,-rpath,"\$ORIGIN/..tReader.so.10svn lib/libLLVMCore.so.10svn lib/libLLVMMC.so.10svn lib/libLLVMMCParser.so.10svn lib/libLLVMSupport.so.10svn lib/libLLVMTextAPI.so.10svn && : lib/Object/CMakeFiles/LLVMObject.dir/ArchiveWriter.cpp.o:ArchiveWriter.cpp:function llvm::writeArchive(llvm::StringRef, llvm::ArrayRef, bool, llvm::object::Archive::Kind, bool, bt_delete >): error: undefined reference to 'llvm::raw_string_ostream::current_pos() const' lib/Object/CMakeFiles/LLVMObject.dir/ArchiveWriter.cpp.o:ArchiveWriter.cpp:function llvm::writeArchive(llvm::StringRef, llvm::ArrayRef, bool, llvm::object::Archive::Kind, bool, bt_delete >): error: undefined reference to 'llvm::raw_string_ostream::current_pos() const' lib/Object/CMakeFiles/LLVMObject.dir/ArchiveWriter.cpp.o:ArchiveWriter.cpp:function llvm::writeArchive(llvm::StringRef, llvm::ArrayRef, bool, llvm::object::Archive::Kind, bool, bt_delete >): error: undefined reference to 'llvm::raw_string_ostream::current_pos() const' lib/Object/CMakeFiles/LLVMObject.dir/ArchiveWriter.cpp.o:ArchiveWriter.cpp:function llvm::writeArchive(llvm::StringRef, llvm::ArrayRef, bool, llvm::object::Archive::Kind, bool, b t_delete >): error: undefined reference to 'llvm::raw_string_ostream::current_pos() const' collect2: error: ld returned 1 exit status Full build log attached -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43234] New: ARM: extraneous unwinder reference with -fprofile-arcs
https://bugs.llvm.org/show_bug.cgi?id=43234 Bug ID: 43234 Summary: ARM: extraneous unwinder reference with -fprofile-arcs Product: clang Version: 8.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: a...@linaro.org CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk I got a link error on a 32-bit ARM kernel build with CONFIG_GCOV_KERNEL and CONFIG_UNWIND_FRAME_POINTER set: kernel/trace/trace_clock.o:(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' kernel/trace/trace_clock.o:(.ARM.exidx+0x8): undefined reference to `__aeabi_unwind_cpp_pr0' kernel/trace/trace_clock.o:(.ARM.exidx+0x10): undefined reference to `__aeabi_unwind_cpp_pr0' I created a reduced test case at https://godbolt.org/z/gBQtAP Basically, clang inserts __llvm_gcov_writeout/__llvm_gcov_flush/__llvm_gcov_init functions into any file it compiles, even for an empty C file input. These functions contain .fnstart/.fnend statements even when building with "-fno-omit-frame-pointer -fno-unwind-tables", which then results in unresolved references to __aeabi_unwind_cpp_pr0. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43233] New: Clang crash on std::pow(n, -0.0)
https://bugs.llvm.org/show_bug.cgi?id=43233
Bug ID: 43233
Summary: Clang crash on std::pow(n, -0.0)
Product: clang
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: zamazan...@tut.by
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
For the code:
#include
double t1(double n) {
return std::pow(n, -0.0);
}
clang (trunk, 8.0) crashes with the follworing message:
https://pastebin.com/w7nVhwtu
clang 7.0 and below works fine.
Godbolt playground: https://godbolt.org/z/aRbTH0
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43225] AVX miscompile at -O2 beginning with r360526
https://bugs.llvm.org/show_bug.cgi?id=43225 Hans Wennborg changed: What|Removed |Added CC||h...@chromium.org Resolution|--- |FIXED Status|REOPENED|RESOLVED --- Comment #6 from Hans Wennborg --- Merged to release_90 in r371178. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 42474] [meta] 9.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=42474 Bug 42474 depends on bug 43225, which changed state. Bug 43225 Summary: AVX miscompile at -O2 beginning with r360526 https://bugs.llvm.org/show_bug.cgi?id=43225 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 42607] [X86] Vectors of __int128 are not passed the same way as gcc in x86-64 ABI
https://bugs.llvm.org/show_bug.cgi?id=42607 Craig Topper changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)||r371169 Status|NEW |RESOLVED --- Comment #5 from Craig Topper --- Fixed in r371169 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
