[llvm-bugs] Issue 5400 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor
Comment #2 on issue 5400 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5400#c2 ClusterFuzz has detected this issue as fixed in range 201802220624:201802230625. Detailed report: https://oss-fuzz.com/testcase?key=4880755009257472 Project: llvm Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer Fuzz target binary: llvm-dwarfdump-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Heap-buffer-overflow READ 1 Crash Address: 0x60b0020e Crash State: llvm::StringMapImpl::LookupBucketFor std::__1::pair, bool> llvm::StringMapllvm:: llvm::object::WasmObjectFile::parseLinkingSectionComdat Sanitizer: address (ASAN) Recommended Security Severity: Medium Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801090613:201801100627 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802220624:201802230625 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4880755009257472 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5953 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::raw_svector_ostream::write_impl
Comment #2 on issue 5953 by ClusterFuzz-External:
llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in
llvm::raw_svector_ostream::write_impl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5953#c2
ClusterFuzz has detected this issue as fixed in range
201802220624:201802230625.
Detailed report: https://oss-fuzz.com/testcase?key=5397097705635840
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-dwarfdump-fuzzer
Fuzz target binary: llvm-dwarfdump-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Heap-buffer-overflow READ {*}
Crash Address: 0x60600111
Crash State:
llvm::raw_svector_ostream::write_impl
llvm::raw_ostream::write
llvm::Twine::printOneChild
Sanitizer: address (ASAN)
Recommended Security Severity: Medium
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201708280446:201708291805
Fixed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802220624:201802230625
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5397097705635840
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
more information.
If you suspect that the result above is incorrect, try re-doing that job on
the test case report page.
--
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
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5400 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 5400 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5400#c3 ClusterFuzz testcase 4880755009257472 is verified as fixed, so closing issue as verified. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 5953 in oss-fuzz: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::raw_svector_ostream::write_impl
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #3 on issue 5953 by ClusterFuzz-External: llvm/llvm-dwarfdump-fuzzer: Heap-buffer-overflow in llvm::raw_svector_ostream::write_impl https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5953#c3 ClusterFuzz testcase 5397097705635840 is verified as fixed, so closing issue as verified. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 3669 in oss-fuzz: llvm: ASSERT: NumParams == params.size() && "function has too many parameters"
Updates: Status: WontFix Comment #8 on issue 3669 by ClusterFuzz-External: llvm: ASSERT: NumParams == params.size() && "function has too many parameters" https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3669#c8 ClusterFuzz testcase 6634601540747264 is flaky and no longer crashes, so closing issue. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36487] New: Compiler crash when cross-compiling lz4
https://bugs.llvm.org/show_bug.cgi?id=36487 Bug ID: 36487 Summary: Compiler crash when cross-compiling lz4 Product: clang Version: trunk Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: LLVM Codegen Assignee: unassignedclangb...@nondot.org Reporter: g...@torproject.org CC: llvm-bugs@lists.llvm.org Created attachment 19934 --> https://bugs.llvm.org/attachment.cgi?id=19934&action=edit lz4-preprocessed source Over at Mozilla's https://bugzilla.mozilla.org/show_bug.cgi?id=1390583 we are trying to get Firefox cross-compiled for Windows using clang. This works thanks to the efforts by Martin Storsjö and others if I compile Firefox 52 ESR (the current long-term support version of Firefox). However, clang crashes during compilation of the latest Mozilla code after lz4 got updated to version 1.8.0. Here is the stack trace and bit of info and attached is the preprocessed source and the associated run script. 1:21.66 #0 0x55d9043c9b9a llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1614b9a) 1:21.66 #1 0x55d9043c7a3e llvm::sys::RunSignalHandlers() (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1612a3e) 1:21.66 #2 0x55d9043c7b8c SignalHandler(int) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1612b8c) 1:21.66 #3 0x7fb418711180 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12180) 1:21.66 #4 0x7fb41724c6a0 gsignal (/lib/x86_64-linux-gnu/libc.so.6+0x346a0) 1:21.66 #5 0x7fb41724dcf7 abort (/lib/x86_64-linux-gnu/libc.so.6+0x35cf7) 1:21.66 #6 0x7fb417244fca (/lib/x86_64-linux-gnu/libc.so.6+0x2cfca) 1:21.66 #7 0x7fb417245042 (/lib/x86_64-linux-gnu/libc.so.6+0x2d042) 1:21.66 #8 0x55d90379fd65 llvm::X86FrameLowering::emitPrologue(llvm::MachineFunction&, llvm::MachineBasicBlock&) const (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x9ead65) 1:21.66 #9 0x55d903d97df8 (anonymous namespace)::PEI::runOnMachineFunction(llvm::MachineFunction&) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0xfe2df8) 1:21.66 #10 0x55d903b9aa35 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0xde5a35) 1:21.66 #11 0x55d903f4d563 llvm::FPPassManager::runOnFunction(llvm::Function&) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1198563) 1:21.66 #12 0x55d903f4d624 llvm::FPPassManager::runOnModule(llvm::Module&) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1198624) 1:21.66 #13 0x55d903f4e241 llvm::legacy::PassManagerImpl::run(llvm::Module&) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1199241) 1:21.66 #14 0x55d904597e0e (anonymous namespace)::EmitAssemblyHelper::EmitAssembly(clang::BackendAction, std::unique_ptr >) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x17e2e0e) 1:21.66 #15 0x55d90459956c clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::HeaderSearchOptions const&, clang::CodeGenOptions const&, clang::TargetOptions const&, clang::LangOptions const&, llvm::DataLayout const&, llvm::Module*, clang::BackendAction, std::unique_ptr >) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x17e456c) 1:21.66 #16 0x55d904cfc104 clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1f47104) 1:21.66 #17 0x55d9051c7340 clang::ParseAST(clang::Sema&, bool, bool) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x2412340) 1:21.66 #18 0x55d904cfb2b9 clang::CodeGenAction::ExecuteAction() (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1f462b9) 1:21.66 #19 0x55d904985236 clang::FrontendAction::Execute() (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1bd0236) 1:21.67 #20 0x55d90494d586 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1b98586) 1:21.67 #21 0x55d904a1ba91 clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x1c66a91) 1:21.67 #22 0x55d903732440 cc1_main(llvm::ArrayRef, char const*, void*) (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x97d440) 1:21.67 #23 0x55d9036e94b5 main (/home/thomas/Arbeit/Tor/debugging/win59/clang_toolchain/bin/clang-7.0+0x9344b5) 1:21.67 #24 0x7fb417238f2a __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x20f2a) 1:21.67 #25 0x55d90372e55a _start (/home/thomas/Arbeit/Tor/debugging/win59/clang_t
[llvm-bugs] [Bug 36488] New: clang-format memory usage increases constantly up to machine crash with very long #define
https://bugs.llvm.org/show_bug.cgi?id=36488 Bug ID: 36488 Summary: clang-format memory usage increases constantly up to machine crash with very long #define Product: clang Version: 5.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: ufosp...@gmail.com CC: djas...@google.com, kli...@google.com, llvm-bugs@lists.llvm.org Created attachment 19936 --> https://bugs.llvm.org/attachment.cgi?id=19936&action=edit File that make clang-format fail The attached 600 lines #define makes clang-format constantly use more memory up to system crash (32 Gb). clang-format -style=LLVM x.cpp tested on linux with clang-format 4.0.1 and 5.0.1. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36475] Unexpected change in layout behaviour for synthetic sections in scripts
https://bugs.llvm.org/show_bug.cgi?id=36475 George Rimar changed: What|Removed |Added Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from George Rimar --- Testcase documenting new behavior added in r325873. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36297] [ELF] - LLD can produce excessive undefined symbols with specific linker script.
https://bugs.llvm.org/show_bug.cgi?id=36297 George Rimar changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from George Rimar --- r325875 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36063] MergedLoadStoreMotion is not actually preserving MemDep
https://bugs.llvm.org/show_bug.cgi?id=36063 Björn Steinbrink changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #5 from Björn Steinbrink --- Fixed in r325880 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36475] Unexpected change in layout behaviour for synthetic sections in scripts
https://bugs.llvm.org/show_bug.cgi?id=36475 James Henderson changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WONTFIX |--- -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35804] [meta] 6.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=35804 Bug 35804 depends on bug 36372, which changed state. Bug 36372 Summary: advapi.lib missing from llvm-config.exe --system-libs on windows https://bugs.llvm.org/show_bug.cgi?id=36372 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36372] advapi.lib missing from llvm-config.exe --system-libs on windows
https://bugs.llvm.org/show_bug.cgi?id=36372 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Blocks||35804 Resolution|--- |FIXED --- Comment #4 from Hans Wennborg --- I suppose this is easy to fix. r325894 and merged to 6.0 in r325895. Andrew, please reopen if there are still problems here. Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=35804 [Bug 35804] [meta] 6.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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 6527 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer Proj-llvm Reported-2018-02-23 Type: Bug New issue 6527 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in ComplexExprEvaluator::VisitBinaryOperator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6527 Detailed report: https://oss-fuzz.com/testcase?key=5861530882015232 Project: llvm Fuzzer: libFuzzer_llvm_clang-fuzzer Fuzz target binary: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7fff41fa7f20 Crash State: ComplexExprEvaluator::VisitBinaryOperator clang::StmtVisitorBasebool>::Visit Sanitizer: address (ASAN) Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5861530882015232 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 35625] Wasm backend: crash on address of aliased function name
https://bugs.llvm.org/show_bug.cgi?id=35625 Nicholas Wilson changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Nicholas Wilson --- Closing; now that we have a proper symbol table, the "hack" involving duplicate imports is no longer needed, and the handling of aliased functions can be considered comprehensively fixed. rLLD325861 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36490] New: Segmentation fault when accessing any Python script object
https://bugs.llvm.org/show_bug.cgi?id=36490 Bug ID: 36490 Summary: Segmentation fault when accessing any Python script object Product: lldb Version: 3.6 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: evg...@loop54.com CC: llvm-bugs@lists.llvm.org Running on Ubuntu 16.04 x64 lldb version 3.6.2 ( revision ) root@linuxtest24:~# lldb-3.6 (lldb) script Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D. >>> print lldb.debugger >>> Segmentation fault (core dumped) The same happens when I try to access other objects like lldb.target or lldb.process. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36490] Segmentation fault when accessing any Python script object
https://bugs.llvm.org/show_bug.cgi?id=36490 lab...@google.com changed: What|Removed |Added CC||lab...@google.com Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #3 from lab...@google.com --- 3.6 is ancient. There isn't anything we could do about your crash even if we found the cause (also, 3.6 had plenty of other issues as well). I'd recommend trying a newer version of the debugger, 3.8 at the very least. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 6528 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-indvars: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-indvars
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, mitchphi...@outlook.com, xpl...@gmail.com, akils...@apple.com Labels: ClusterFuzz Reproducible Engine-libfuzzer Proj-llvm Reported-2018-02-23 Type: Bug New issue 6528 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-indvars: Out-of-memory in llvm_llvm-opt-fuzzer--x86_64-indvars https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6528 Detailed report: https://oss-fuzz.com/testcase?key=5718388618821632 Project: llvm Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-indvars Fuzz target binary: llvm-opt-fuzzer--x86_64-indvars Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Out-of-memory (exceeds 2048 MB) Crash Address: Crash State: llvm_llvm-opt-fuzzer--x86_64-indvars Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802210603:201802211531 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5718388618821632 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information. When you fix this bug, please * mention the fix revision(s). * state whether the bug was a short-lived regression or an old bug in any stable releases. * add any other useful information. This information can help downstream consumers. If you have questions for the OSS-Fuzz team, please file an issue at https://github.com/google/oss-fuzz/issues. -- 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36491] New: Undesirable rematerialization of stack address computation
https://bugs.llvm.org/show_bug.cgi?id=36491
Bug ID: 36491
Summary: Undesirable rematerialization of stack address
computation
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Backend: AArch64
Assignee: unassignedb...@nondot.org
Reporter: eugeni.stepa...@gmail.com
CC: llvm-bugs@lists.llvm.org
$ cat 1.c
void use(void *);
void *p;
void f() {
int x;
p = &x;
use(&x);
}
$ bin/clang 1.c -target aarch64-linux-android -O3 -fomit-frame-pointer -c &&
bin/llvm-objdump -d -r 1.o
0: fe 0f 1f f8 str x30, [sp, #-16]!
4: 08 00 00 90 adrpx8, #0
0004: R_AARCH64_ADR_PREL_PG_HI21 p
8: e9 33 00 91 add x9, sp, #12
c: e0 33 00 91 add x0, sp, #12
10: 09 01 00 f9 str x9, [x8]
0010: R_AARCH64_LDST64_ABS_LO12_NC p
14: 00 00 00 94 bl #0
0014: R_AARCH64_CALL26 use
18: fe 07 41 f8 ldr x30, [sp], #16
1c: c0 03 5f d6 ret
Here x0 and x9 could be merged, but RegisterCoalescer would never consider
merging into a physical register. Instead it remats ADDXri %stack.0.x, 0, 0.
This is specific to AArch64 backend. The same does not happen on X86 because
ADDXri is asCheapAsAMove, while LEA is not.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36492] New: FileCheck cannot match a particular regex combination
https://bugs.llvm.org/show_bug.cgi?id=36492
Bug ID: 36492
Summary: FileCheck cannot match a particular regex combination
Product: Test Suite
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: lit
Assignee: unassignedb...@nondot.org
Reporter: rafael.espind...@gmail.com
CC: dan...@zuster.org, llvm-bugs@lists.llvm.org
Given
$ cat foo
foo foo foo
foo
foo foo
foo foo foo
foo foo foo
foo foo foo
foo foo foo
$ cat check
CHECK: foo foo foo
CHECK: foo [[ABC:foo]] foo
CHECK: foo [[ABC:foo]] [[ABC]]
CHECK: {{.*}} [[ABC:foo]] [[ABC]]
CHECK: {{(foo)}} [[ABC:foo]] [[ABC]]
CHECK: {{(foo)?}} [[ABC:foo]] [[ABC]]
Only the last line fails to match:
$ FileCheck check < foo
check:6:8: error: expected string not found in input
CHECK: {{(foo)?}} [[ABC:foo]] [[ABC]]
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 31617] avx512 : blendm, missing instruction form.
https://bugs.llvm.org/show_bug.cgi?id=31617 Craig Topper changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #2 from Craig Topper --- Fixed in r325957 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 10988] x86 MC encoder and disassembler bugs umbrella
https://bugs.llvm.org/show_bug.cgi?id=10988 Bug 10988 depends on bug 31617, which changed state. Bug 31617 Summary: avx512 : blendm, missing instruction form. https://bugs.llvm.org/show_bug.cgi?id=31617 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36435] Unexpected conditional breakpoint hit
https://bugs.llvm.org/show_bug.cgi?id=36435 Jim Ingham changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Jim Ingham --- Ack, that's my bad. Fixed in r325958. Thanks for reporting this! -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 6156 in oss-fuzz: llvm: Stack-overflow in clang::Sema::GetNameFromUnqualifiedId
Updates: Status: WontFix Comment #2 on issue 6156 by ClusterFuzz-External: llvm: Stack-overflow in clang::Sema::GetNameFromUnqualifiedId https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6156#c2 ClusterFuzz testcase 6754063296233472 is flaky and no longer crashes, so closing issue. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36493] New: clang windows is emitting column information
https://bugs.llvm.org/show_bug.cgi?id=36493
Bug ID: 36493
Summary: clang windows is emitting column information
Product: libraries
Version: trunk
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: DebugInfo
Assignee: unassignedb...@nondot.org
Reporter: ztur...@google.com
CC: llvm-bugs@lists.llvm.org
In theory, CodeView supports column information. However, most windows
debuggers don't recognize it and -- worse -- behave incorrectly in the presence
of column information. If you compile this program with clang on Windows:
int f(int, int);
# 1 "F:\\git\\fastbuild\\Code\\Tools\\FBuild\\FBuildApp\\Main.cpp"
int g;
int i() {
# 83
return f(g, g);
}
it will generate LLVM assembly that looks like this:
.cv_loc 0 1 83 15 #
F:\git\fastbuild\Code\Tools\FBuild\FBuildApp\Main.cpp:83:15
movl"?g@@3HA", %eax
.cv_loc 0 1 83 12 #
F:\git\fastbuild\Code\Tools\FBuild\FBuildApp\Main.cpp:83:12
movl"?g@@3HA", %ecx
.cv_loc 0 1 83 10 #
F:\git\fastbuild\Code\Tools\FBuild\FBuildApp\Main.cpp:83:10
movl%ecx, (%esp)
What this is trying to say is that there are 3 different addresses for line 83,
corresponding to columns 10, 12, and 15 respectively. But the debugger simply
interprets this as "there are 3 addresses for line 83", and as a result you
have to hit the step button 3 times to get to the next statement.
This seems like a regression, as I don't recall us emitting this before. At
the very least, the debugger was working on step over before as far as I
remember.
We will need to stop emitting cv_loc directives at column granularity. Note
that -dwarf-column-info was not passed on the command line here. The arguments
used were:
r"d:\src\llvmbuild\cl\Release\x64\bin\clang++.exe",
"-std=c++11",
r"Main.cpp",
"-c",
"-g3",
"-gcodeview",
"-Wall",
"-Werror",
"-Wfatal-errors",
"-Wextra",
"-DWIN32_LEAN_AND_MEAN",
"-D_WIN32",
"-D__WINDOWS__",
"-DWIN32",
"-D_CRT_SECURE_NO_WARNINGS",
"-D_WINSOCK_DEPRECATED_NO_WARNINGS",
"-m32",
"-D_X86_=1",
"-D_INTEGRAL_MAX_BITS=64",
"-D_MT",
"-fms-compatibility",
"-fms-extensions",
"-fmsc-version=1900",
"-Wno-#pragma-messages",
"-Wno-unknown-pragmas",
"-Wno-unused-function",
"-Wno-microsoft",
"-Wno-unused-value",
"-Wno-ignored-attributes",
"-Wno-incompatible-ms-struct",
"-Wno-nonportable-include-path",
"-Wno-ignored-pragma-intrinsic",
"-Wno-invalid-token-paste",
"-Wno-implicit-exception-spec-mismatch",
"-Wshadow",
"-fno-rtti",
"-Xclang",
"-flto-visibility-public-std",
"-DDEBUG",
"-DPROFILING_ENABLED",
"-O0",
"-S"]
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36494] New: TestBase.LaunchModePreservesEnvironment is failing on Darwin
https://bugs.llvm.org/show_bug.cgi?id=36494 Bug ID: 36494 Summary: TestBase.LaunchModePreservesEnvironment is failing on Darwin Product: lldb Version: unspecified Hardware: PC OS: MacOS X Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-...@lists.llvm.org Reporter: v...@apple.com CC: llvm-bugs@lists.llvm.org With r325964, I see: [ RUN ] TestBase.LaunchModePreservesEnvironment /Users/vsk/src/llvm.org-lldbsan/llvm/tools/lldb/unittests/tools/lldb-server/tests/LLGSTest.cpp:30: Failure Value of: llvm::detail::TakeExpected(Client.GetLatestStopReplyAs()) Expected: succeeded with value (is an object whose given property is equal to 2-byte object <00-00>) Actual: succeeded with value 16-byte object <10-60 A7-04 01-00 00-00 01-00 00-00 00-00 00-30>, whose given property is 2-byte object <00-01>(is an object whose given property isn't equal to 2-byte object <00-00>) [ FAILED ] TestBase.LaunchModePreservesEnvironment (67 ms) The public Darwin bots are failing in the same way, but curiously still appear 'green'. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 6187 in oss-fuzz: llvm: Stack-overflow in UnqualUsingDirectiveSet::visitScopeChain
Updates: Status: WontFix Comment #1 on issue 6187 by ClusterFuzz-External: llvm: Stack-overflow in UnqualUsingDirectiveSet::visitScopeChain https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6187#c1 ClusterFuzz testcase 6687347891503104 is flaky and no longer crashes, so closing issue. 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 http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36494] TestBase.LaunchModePreservesEnvironment is failing on Darwin
https://bugs.llvm.org/show_bug.cgi?id=36494 Vedant Kumar changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Vedant Kumar --- Great, I implemented your suggestion in r326001. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36495] New: SLP-vectorized function doesn't get inlined
https://bugs.llvm.org/show_bug.cgi?id=36495 Bug ID: 36495 Summary: SLP-vectorized function doesn't get inlined Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Global Analyses Assignee: unassignedb...@nondot.org Reporter: timshe...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 19945 --> https://bugs.llvm.org/attachment.cgi?id=19945&action=edit Test In the test case, MinByVal should inline its call to Min, given that Min is sufficiently short *after* SLP Vectorization. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36496] New: Non-optimal result for SSE min() vectorization
https://bugs.llvm.org/show_bug.cgi?id=36496 Bug ID: 36496 Summary: Non-optimal result for SSE min() vectorization Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Backend: X86 Assignee: unassignedb...@nondot.org Reporter: timshe...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 19946 --> https://bugs.llvm.org/attachment.cgi?id=19946&action=edit Test The test shows that changing "a < b ? a : b" to "b < a ? b : a" causes a codegen difference, even though semantically they are the same. -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36221] Support for the mno-stack-arg-probe flag
https://bugs.llvm.org/show_bug.cgi?id=36221 Ruslan Nikolaev changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Ruslan Nikolaev --- Merged. More recent patches & review: https://reviews.llvm.org/D43107 https://reviews.llvm.org/D43108 -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36498] New: clang frontend command failed due to signal
https://bugs.llvm.org/show_bug.cgi?id=36498
Bug ID: 36498
Summary: clang frontend command failed due to signal
Product: clang
Version: 5.0
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Frontend
Assignee: unassignedclangb...@nondot.org
Reporter: s...@list.ru
CC: llvm-bugs@lists.llvm.org
Created attachment 19947
--> https://bugs.llvm.org/attachment.cgi?id=19947&action=edit
test-case
The following simple test-case makes clang++ to segfault:
---
void operator delete(void *) {}
#include
void operator delete(void *) {}
---
$ clang++ -c -std=c++11 tst.cpp
clang-5.0: error: unable to execute command: Segmentation fault (core dumped)
clang-5.0: error: clang frontend command failed due to signal (use -v to see
invocation)
Without -std=c++11 there is no segfault.
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 36499] New: No completion for incomplete type alias
https://bugs.llvm.org/show_bug.cgi?id=36499
Bug ID: 36499
Summary: No completion for incomplete type alias
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: libclang
Assignee: unassignedclangb...@nondot.org
Reporter: dummymail...@gmail.com
CC: kli...@google.com, llvm-bugs@lists.llvm.org
libclang seems to have added support for completion of incomplete types, but a
trivial type alias cause it to break:
template struct A { void foo(); };
template using B = A;
template struct C {
A a;
B b;
C() {
// a. completes
// b. doesn't complete
}
};
Completion for a. gives:
❯❯❯ c-index-test -code-completion-at=sample.cpp:9:11 sample.cpp
StructDecl:{TypedText A}{Text ::} (75)
CXXMethod:{ResultType void}{TypedText foo}{LeftParen (}{RightParen )} (34)
NotImplemented:{TypedText template} (40)
Completion contexts:
Dot member access
Completion for b. gives:
❯❯❯ c-index-test -code-completion-at=sample.cpp:9:11 sample.cpp
Completion contexts:
Dot member access
--
You are receiving this mail because:
You are on the CC list for the bug.___
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
