[llvm-bugs] [Bug 40598] New: diagnostics: "no return statement in constexpr function" when return exists but has bad type
https://bugs.llvm.org/show_bug.cgi?id=40598
Bug ID: 40598
Summary: diagnostics: "no return statement in constexpr
function" when return exists but has bad type
Product: clang
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: com...@gmail.com
CC: blitzrak...@gmail.com, dgre...@apple.com,
erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org,
richard-l...@metafoo.co.uk
Given
constexpr int foo() {
return "asdf";
}
Clang produces:
:2:12: error: cannot initialize return object of type 'int' with an
lvalue of type 'const char [5]'
return "asdf";
^~
:1:15: error: no return statement in constexpr function
constexpr int foo() {
The second error is clearly unhelpful in this case.
--
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 40597] New: Error whlle compiling C++ with polly
https://bugs.llvm.org/show_bug.cgi?id=40597 Bug ID: 40597 Summary: Error whlle compiling C++ with polly Product: Polly Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Other Assignee: polly-...@googlegroups.com Reporter: pradeepisr...@gmail.com CC: llvm-bugs@lists.llvm.org The following error was printed when I ran clang with polly: Command: clang -Xclang -load -Xclang LLVMPolly.so polly_test.cpp clang version 9.0.0 (http://llvm.org/git/clang.git 44d861c1f7099970b74af95998dc36e99eeb1f08) (http://llvm.org/git/llvm.git 911c696716fbcfc90f4f105f81ffacca4f7868ea) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: [Path to Polly]/Polly/llvm_build//bin Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6 Found candidate GCC installation: /usr/lib/gcc/i686-linux-gnu/6.0.0 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6 Found candidate GCC installation: /usr/lib/gcc/x86_64-linux-gnu/6.0.0 Selected GCC installation: /usr/lib/gcc/x86_64-linux-gnu/5.4.0 Candidate multilib: .;@m64 Selected multilib: .;@m64 Found CUDA installation: /usr/local/cuda-9.2, version 9.2 "[Path to Polly]/Polly/llvm_build/bin/clang-9" -cc1 -triple x86_64-unknown-linux-gnu -emit-obj -mrelax-all -disable-free -main-file-name polly_test.cpp -mrelocation-model static -mthread-model posix -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64 -dwarf-column-info -debugger-tuning=gdb -v -resource-dir [Path to Polly]/Polly/llvm_build/lib/clang/9.0.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/x86_64-linux-gnu/c++/5.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/x86_64-linux-gnu/c++/5.4.0 -internal-isystem /usr/lib/gcc/x86_64-linux-gnu/5.4.0/../../../../include/c++/5.4.0/backward -internal-isystem /usr/local/include -internal-isystem [Path to Polly]/Polly/llvm_build/lib/clang/9.0.0/include -internal-externc-isystem /usr/include/x86_64-linux-gnu -internal-externc-isystem /include -internal-externc-isystem /usr/include -fdeprecated-macro -fdebug-compilation-dir [Path to Polly]/C++ -ferror-limit 19 -fmessage-length 211 -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -load [Path to Polly]/Polly/llvm_build//lib/LLVMPolly.so -mllvm -polly -o /tmp/polly_test-f8fc45.o -x c++ polly_test.cpp -faddrsig : CommandLine Error: Option 'polly-dependences-computeout' registered more than once! fatal error: error in backend: inconsistency in registered CommandLine options clang-9: error: clang frontend command failed with exit code 70 (use -v to see invocation) clang version 9.0.0 (http://llvm.org/git/clang.git 44d861c1f7099970b74af95998dc36e99eeb1f08) (http://llvm.org/git/llvm.git 911c696716fbcfc90f4f105f81ffacca4f7868ea) Target: x86_64-unknown-linux-gnu Thread model: posix InstalledDir: [Path to Polly]/Polly/llvm_build//bin clang-9: note: diagnostic msg: PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash backtrace, preprocessed source, and associated run script. clang-9: note: diagnostic msg: Error generating preprocessed source(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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40514] [LSR] Assertion `!BaseReg->isZero() && "Zero allocated in a base register!"' failed.
https://bugs.llvm.org/show_bug.cgi?id=40514 Max Kazantsev changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Max Kazantsev --- https://reviews.llvm.org/rL353136 -- 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 38300] [dr1992] Wrong exception deduction for some forms of placement new
https://bugs.llvm.org/show_bug.cgi?id=38300 hst...@ca.ibm.com changed: What|Removed |Added CC||hst...@ca.ibm.com Resolution|--- |WONTFIX Status|REOPENED|RESOLVED --- Comment #4 from hst...@ca.ibm.com --- The behaviour requested by the originator is the opposite of what DR1992 requires. For actually performing a check (instead of calling the allocation function), we have https://llvm.org/PR35573. -- 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 40506] [Wasm] llvm-objdump prints `call` as `except_ref.call`
https://bugs.llvm.org/show_bug.cgi?id=40506 Wouter van Oortmerssen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Wouter van Oortmerssen --- Fixed here: https://reviews.llvm.org/D57713 Fixes it for call, end, and v128.const.. any others can easily be added with IsCanonical in .td files. -- 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 12903 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@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 Proj-llvm Reported-2019-02-05 Type: Bug New issue 12903 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in llvm::StringMapImpl::LookupBucketFor https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12903 Detailed report: https://oss-fuzz.com/testcase?key=5769629396369408 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: 0x7ffc93df6f28 Crash State: llvm::StringMapImpl::LookupBucketFor std::__1::pair, bool> llvm::Stri clang::Preprocessor::LookUpIdentifierInfo Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201902030422:201902040424 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5769629396369408 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12902 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Lexer::LexTokenInternal
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@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 Proj-llvm Reported-2019-02-05 Type: Bug New issue 12902 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Lexer::LexTokenInternal https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12902 Detailed report: https://oss-fuzz.com/testcase?key=5183672309776384 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: 0x7ffe2f050ea0 Crash State: clang::Lexer::LexTokenInternal clang::Lexer::Lex clang::Preprocessor::Lex Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201902030422:201902040424 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5183672309776384 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40257] Build failure using clang + libstdc++ from gcc 9
https://bugs.llvm.org/show_bug.cgi?id=40257 Romain Geissler changed: What|Removed |Added Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #3 from Romain Geissler --- This is actually a libstdc++ issue, reported and fixed in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88840 -- 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 38866] WebAssembly- assertion failure with alias for function
https://bugs.llvm.org/show_bug.cgi?id=38866 Sam Clegg changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- 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 40596] New: Merge r352555 into the 8.0 branch
https://bugs.llvm.org/show_bug.cgi?id=40596 Bug ID: 40596 Summary: Merge r352555 into the 8.0 branch Product: libraries Version: 8.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Transformation Utilities Assignee: unassignedb...@nondot.org Reporter: l...@meinersbur.de CC: llvm-bugs@lists.llvm.org Blocks: 40331 Simple fix to avoid a false warning; https://reviews.llvm.org/D57260 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=40331 [Bug 40331] [meta] 8.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 40546] omp simd reduction "loop not vectorized" warning for a simple loop that even seems vectorized
https://bugs.llvm.org/show_bug.cgi?id=40546 Michael Kruse changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Fixed By Commit(s)||r353082 -- 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 40595] New: Merge r352945 into the 8.0 branch
https://bugs.llvm.org/show_bug.cgi?id=40595 Bug ID: 40595 Summary: Merge r352945 into the 8.0 branch Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Core LLVM classes Assignee: unassignedb...@nondot.org Reporter: efrie...@quicinc.com CC: llvm-bugs@lists.llvm.org Blocks: 40331 Simple bugfix for autoupgrade; https://reviews.llvm.org/rL352945 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=40331 [Bug 40331] [meta] 8.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 40592] Regression(352138:352921): Assertion failed: (mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match") when building boringssl for aarch64
https://bugs.llvm.org/show_bug.cgi?id=40592 Matt Arsenault changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #7 from Matt Arsenault --- r353069 -- 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 40593] New: Test case clangd/background-index.test fails when path contains special characters
https://bugs.llvm.org/show_bug.cgi?id=40593 Bug ID: 40593 Summary: Test case clangd/background-index.test fails when path contains special characters Product: clang-tools-extra Version: unspecified Hardware: All OS: Linux Status: NEW Severity: normal Priority: P Component: clangd Assignee: unassignedclangb...@nondot.org Reporter: amy.kw...@ibm.com CC: llvm-bugs@lists.llvm.org The following test case exhibits failures on PowerPC: Clang Tools :: clangd/background-index.test This test was introduced in https://reviews.llvm.org/rL347567. It checks for paths to files that are produced. The failures occur when the path to the files contain special characters, such as '+'. Due to paths with these characters, the clangd test case will not recognize them because there is a CHECK: "uri" string. The CHECK string, for example, will expect a path with the directory named "build+dir", but the actual input is instead "build%2Bdir". Special characters such as '+' is being escaped in the actual URI input so it will result a failure. -- 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 12899 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::Parser::ParseAssignmentExpression
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@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 Proj-llvm Reported-2019-02-04 Type: Bug New issue 12899 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::Parser::ParseAssignmentExpression https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12899 Detailed report: https://oss-fuzz.com/testcase?key=4781412996612096 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: 0x7ffd80c10ca0 Crash State: clang::Parser::ParseAssignmentExpression clang::Parser::ParseRHSOfBinaryExpression clang::Parser::ParseRHSOfBinaryExpression Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201710121744:201710130454 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4781412996612096 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40592] New: Regression(352138:352921): Assertion failed: (mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match") when building boringssl for aarch64
https://bugs.llvm.org/show_bug.cgi?id=40592 Bug ID: 40592 Summary: Regression(352138:352921): Assertion failed: (mutationIsSane(Rule, Query, Mutation) && "legality mutation invalid for match") when building boringssl for aarch64 Product: libraries Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: GlobalISel Assignee: unassignedb...@nondot.org Reporter: nicolaswe...@gmx.de CC: llvm-bugs@lists.llvm.org, quentin.colom...@gmail.com Repro 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 40591] New: Symbolizer should ignore undefined symbols
https://bugs.llvm.org/show_bug.cgi?id=40591 Bug ID: 40591 Summary: Symbolizer should ignore undefined symbols Product: tools Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: llvm-symbolizer Assignee: unassignedb...@nondot.org Reporter: jh7370.2...@my.bristol.ac.uk CC: llvm-bugs@lists.llvm.org llvm-symbolizer currently treats undefined symbols as symbols at address 0 and so if 0 is specified as an input address, it will find that symbol, even if there is a defined symbol at that location. I wrote a lit test to reproduce this issue: # symbolize-undef-syms.s # REQUIRES: x86-registered-target # RUN: llvm-mc --filetype=obj --triple=x86_64-pc-linux %s -o %t.o -g # RUN: llvm-symbolizer --obj=%t.o 0 | FileCheck %s --implicit-check-not=bar # CHECK: foo # CHECK-NEXT: symbolize-undef-syms.s:14:0 .type bar,@function .type foo,@function .global foo foo: call bar This test will fail because bar was picked instead of foo. It would be good to never pick bar, even if there is no defined symbol, since bar cannot represent that address. -- 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 37202] LCSSA (Loop-Closed SSA Form Pass) (and hence LICM) is extremely slow
https://bugs.llvm.org/show_bug.cgi?id=37202 Florian Hahn changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Florian Hahn --- With the 2 improvements below, the time spent on the benchmark went from 51s to 19s on my machine. LCSSA first shows up with -time-passes at position 6 or so. https://reviews.llvm.org/rL352960 https://reviews.llvm.org/rL351567 -- 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 12898 in oss-fuzz: llvm/clangd-fuzzer: Stack-overflow in llvm::json::Parser::parseValue
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@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 Proj-llvm Reported-2019-02-04 Type: Bug New issue 12898 by ClusterFuzz-External: llvm/clangd-fuzzer: Stack-overflow in llvm::json::Parser::parseValue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12898 Detailed report: https://oss-fuzz.com/testcase?key=5732132821925888 Project: llvm Fuzzer: libFuzzer_llvm_clangd-fuzzer Fuzz target binary: clangd-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffe9502ef88 Crash State: llvm::json::Parser::parseValue Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5732132821925888 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12897 in oss-fuzz: llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in llvm::ms_demangle::Node** llvm::ms_demangle::ArenaAllocator::allocArray
Status: New
Owner:
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,
igm...@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 Proj-llvm Security_Severity-High Reported-2019-02-04
Type: Bug-Security
New issue 12897 by ClusterFuzz-External:
llvm/llvm-microsoft-demangle-fuzzer: Heap-buffer-overflow in
llvm::ms_demangle::Node**
llvm::ms_demangle::ArenaAllocator::allocArray
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12897
Detailed report: https://oss-fuzz.com/testcase?key=5647811742269440
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-microsoft-demangle-fuzzer
Fuzz target binary: llvm-microsoft-demangle-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Heap-buffer-overflow WRITE {*}
Crash Address: 0x62130900
Crash State:
llvm::ms_demangle::Node**
llvm::ms_demangle::ArenaAllocator::allocArray
llvm::ms_demangle::Demangler::demangleArrayType
llvm::ms_demangle::Demangler::demangleType
Sanitizer: address (ASAN)
Recommended Security Severity: High
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201901070410:201901080410
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5647811742269440
Issue filed automatically.
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
instructions to reproduce this bug locally.
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 need to contact the OSS-Fuzz team with a question, concern, or any
other feedback, 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
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 12894 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@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 Proj-llvm Reported-2019-02-04 Type: Bug New issue 12894 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12894 Detailed report: https://oss-fuzz.com/testcase?key=5181233204559872 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: 0x7ffc6fe46c48 Crash State: clang::FunctionProtoType::getExtProtoInfo clang::FunctionProtoType::Profile llvm::ContextualFoldingSetclang::ASTContext&>::NodeEq Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm=201901220414:201902020421 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5181233204559872 Issue filed automatically. See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. 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 need to contact the OSS-Fuzz team with a question, concern, or any other feedback, 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40590] New: __m64 name mangling different than GCC:
https://bugs.llvm.org/show_bug.cgi?id=40590 Bug ID: 40590 Summary: __m64 name mangling different than GCC: Product: clang Version: 8.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: -New Bugs Assignee: unassignedclangb...@nondot.org Reporter: erich.ke...@intel.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk See https://godbolt.org/z/uzbzu3 GCC mangles the __m64 type as "Dv2_i", but Clang mangles it as "Dv1_x". -- 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 11362 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Subtarget.isCallingConvWin64(MF.getFunction().getCallingConv()) && "Funclets sho
Updates: Labels: Deadline-Approaching Comment #2 on issue 11362 by sheriff...@chromium.org: llvm/llvm-isel-fuzzer--aarch64-gisel: ASSERT: Subtarget.isCallingConvWin64(MF.getFunction().getCallingConv()) && "Funclets sho https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=11362#c2 This bug is approaching its deadline for being fixed, and will be automatically derestricted within 7 days. If a fix is planned within 2 weeks after the deadline has passed, a grace extension can be granted. - Your friendly Sheriffbot -- 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 40589] New: Merge 352928+352929 to 8.0: [COFF] Create range extension thunks for ARM64
https://bugs.llvm.org/show_bug.cgi?id=40589 Bug ID: 40589 Summary: Merge 352928+352929 to 8.0: [COFF] Create range extension thunks for ARM64 Product: new-bugs Version: 8.0 Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: dma...@mozilla.com CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org, mar...@martin.st, r...@google.com Depends on: 40467 Blocks: 40331 Rounds out the COFF/ARM64 work, enables large -O0 builds. https://bugs.llvm.org/show_bug.cgi?id=40467 https://reviews.llvm.org/D57574 https://reviews.llvm.org/rL352928 https://reviews.llvm.org/D57575 https://reviews.llvm.org/rL352929 Referenced Bugs: https://bugs.llvm.org/show_bug.cgi?id=40331 [Bug 40331] [meta] 8.0.0 Release Blockers https://bugs.llvm.org/show_bug.cgi?id=40467 [Bug 40467] -O0 builds get "relocation out of range" in applyArm64Branch26 -- 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 40588] New: NativeProcessLinux::MonitorCallback incorrectly logs value of libc "signal" function
https://bugs.llvm.org/show_bug.cgi?id=40588
Bug ID: 40588
Summary: NativeProcessLinux::MonitorCallback incorrectly logs
value of libc "signal" function
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: lldb-...@lists.llvm.org
Reporter: jcowgill+l...@jcowgill.uk
CC: llvm-bugs@lists.llvm.org
In commit 4d99ca2308f9 ("Add pretty-printer for wait(2) statuses and modernize
the code handling them"), the "signal" parameter was removed from
NativeProcessLinux::MonitorCallback. Unfortunately not all uses of this
parameter were removed and as a result these uses now refer to the "signal"
function from libc which is probably unintended!
Both users are debug logging calls.
Call 1:
LLDB_LOG(log, "got exit signal({0}) , tid = {1} ({2} main thread)", signal,
pid, is_main_thread ? "is" : "is not");
Call 2:
LLDB_LOG(log,
"GetSignalInfo failed: {0}, tid = {1}, signal = {2}, "
"status = {3}, main_thread = {4}, thread_found: {5}",
info_err, pid, signal, status, is_main_thread, thread_found);
--
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 40587] New: EmitFuncArgumentDbgValue hoists DBG_VALUE instructions too aggressively (or rather too often)
https://bugs.llvm.org/show_bug.cgi?id=40587
Bug ID: 40587
Summary: EmitFuncArgumentDbgValue hoists DBG_VALUE instructions
too aggressively (or rather too often)
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Keywords: wrong-debug
Severity: enhancement
Priority: P
Component: Common Code Generator Code
Assignee: unassignedb...@nondot.org
Reporter: bjorn.a.petters...@ericsson.com
CC: david.stenb...@ericsson.com,
jeremy.morse.l...@gmail.com, llvm-bugs@lists.llvm.org
Created attachment 21428
--> https://bugs.llvm.org/attachment.cgi?id=21428=edit
current result on trunk (faulty)
The usage of SelectionDAGBuilder::EmitFuncArgumentDbgValue() seems to sometime
result in incorrect hoisting of dbg.value intrinsics to the top of the entry
block. The function checks if the debug intrinsic's value is an argument, and
if so, creates a DBG_VALUE instruction and adds it to FuncInfo.ArgDbgValues,
which later results in the DBG_VALUE being emitted at the top of the entry
block. It does all this without taking any concern if the described DIVariable
itself is an argument.
Consider this example:
-
extern void bar(int);
void foo_local(int a) {
int local = 123;
bar(local);
local = a;
bar(local);
}
void foo_other_param(int a, int b) {
bar(b);
b = 123;
bar(b);
b = a;
bar(b);
}
void foo_same_param(int a) {
bar(a);
int tmp = a;
a = 123;
bar(a);
a = tmp;
bar(a);
}
-
If I compiler the above using
clang -g -O1 -S -mllvm -stop-before=expand-isel-pseudos
I get output as in "faulty.mir", whereas I'd like to get something similar to
"wanted.mir" (see attachments).
The interesting diff between those mir files is shown here (faulty to the left,
wanted to the right) (also attached as "diff.txt") :
--- |
--- |
; ModuleID = 'foo.c'
; ModuleID = 'foo.c'
source_filename = "foo.c"
source_filename = "foo.c"
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target datalayout =
"e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
target triple = "x86_64-unknown-linux-gnu"
; Function Attrs: nounwind uwtable
; Function Attrs: nounwind uwtable
define dso_local void @foo_local(i32 %a) local_unnamed_addr #0 !dbg !7 {
define dso_local void @foo_local(i32 %a)
local_unnamed_addr #0 !dbg !7 {
entry:
entry:
call void @llvm.dbg.value(metadata i32 %a, metadata !12, metadata
!DIExpression()), !dbg !14call void @llvm.dbg.value(metadata i32
%a, metadata !12, metadata !DIExpression()), !dbg !14
call void @llvm.dbg.value(metadata i32 123, metadata !13, metadata
!DIExpression()), !dbg !1call void @llvm.dbg.value(metadata i32
123, metadata !13, metadata !DIExpression()), !dbg !1
tail call void @bar(i32 123) #3, !dbg !16
tail call void @bar(i32 123) #3, !dbg !16
call void @llvm.dbg.value(metadata i32 %a, metadata !13, metadata
!DIExpression()), !dbg !15call void @llvm.dbg.value(metadata i32
%a, metadata !13, metadata !DIExpression()), !dbg !15
tail call void @bar(i32 %a) #3, !dbg !17
tail call void @bar(i32 %a) #3, !dbg !17
ret void, !dbg !18
ret void, !dbg !18
}
}
declare dso_local void @bar(i32) local_unnamed_addr #1
declare dso_local void @bar(i32) local_unnamed_addr
#1
; Function Attrs: nounwind uwtable
; Function Attrs: nounwind uwtable
define dso_local void @foo_other_param(i32 %a, i32 %b) local_unnamed_addr #0
!dbg !19 { define dso_local void @foo_other_param(i32 %a, i32
%b) local_unnamed_addr #0 !dbg !19 {
entry:
entry:
call void @llvm.dbg.value(metadata i32 %a, metadata !23, metadata
[llvm-bugs] [Bug 40586] New: [MemorySSA] wrong code
https://bugs.llvm.org/show_bug.cgi?id=40586 Bug ID: 40586 Summary: [MemorySSA] wrong code Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: Global Analyses Assignee: unassignedb...@nondot.org Reporter: pauls...@linux.vnet.ibm.com CC: llvm-bugs@lists.llvm.org Created attachment 21427 --> https://bugs.llvm.org/attachment.cgi?id=21427=edit reduced testcase I have seen plenty of wrong code cases with -enable-mssa-loop-dependency the last two weeks (in testing), and have now reduced one program. gcc -O0 -march=z10 -o a.out gcc -O1 -march=z10 -o a.out gcc -O0 -march=z13 -o a.out gcc -O1 -march=z13 -o a.out clang -O0 -march=z10 -o a.out clang -O0 -march=z13 -o a.out clang -O3 -march=z10 -o a.out clang -O3 -march=z13 -o a.out The above programs all print "5", but this one prints "0": clang -O3 -march=z13 -o a.out -mllvm -enable-mssa-loop-dependency -- 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 40584] New: Android (5058415 based on r339409) clang version 8.0.2 compiler crash
https://bugs.llvm.org/show_bug.cgi?id=40584 Bug ID: 40584 Summary: Android (5058415 based on r339409) clang version 8.0.2 compiler crash Product: clang Version: 8.0 Hardware: PC OS: Linux Status: NEW Severity: enhancement Priority: P Component: C++11 Assignee: unassignedclangb...@nondot.org Reporter: headupinclo...@gmail.com CC: blitzrak...@gmail.com, dgre...@apple.com, erik.pilking...@gmail.com, llvm-bugs@lists.llvm.org, richard-l...@metafoo.co.uk Created attachment 21425 --> https://bugs.llvm.org/attachment.cgi?id=21425=edit generated bash script Stack trace: 1. parser at end of file 2. Code generation 3. Running pass 'Function Pass Manager' on module '/home/dhirvonen/.hunter/_Base/f58bcf2/01c698c/47d638b/Build/xgboost/Source/src/gbm/gbm.cpp'. 4. Running pass 'AArch64 Instruction Selection' on function '@_ZN7xgboost4tree9TreeModelIfNS0_13RTreeNodeStatEEC2Ev' #0 0x0234c8c6 llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x234c8c6) #1 0x0234b4d0 llvm::sys::RunSignalHandlers() (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x234b4d0) #2 0x0234cbaa (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x234cbaa) #3 0x7efd50230890 __restore_rt (/lib/x86_64-linux-gnu/libpthread.so.0+0x12890) #4 0x7efd4f28ce97 gsignal /build/glibc-OTsEL5/glibc-2.27/signal/../sysdeps/unix/sysv/linux/raise.c:51:0 #5 0x7efd4f28e801 abort /build/glibc-OTsEL5/glibc-2.27/stdlib/abort.c:81:0 #6 0x022f5920 llvm::report_bad_alloc_error(char const*, bool) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x22f5920) #7 0x01863412 (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x1863412) #8 0x0230d819 llvm::SmallVectorBase::grow_pod(void*, unsigned long, unsigned long) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x230d819) #9 0x01dee0cd (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x1dee0cd) #10 0x01e6022d llvm::SUnit::ComputeDepth() (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x1e6022d) #11 0x029e7cfc (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29e7cfc) #12 0x029e77de (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29e77de) #13 0x029e810a (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29e810a) #14 0x029e7f80 (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29e7f80) #15 0x029e1da6 (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29e1da6) #16 0x029e19e5 (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29e19e5) #17 0x029e168a (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29e168a) #18 0x029d7feb llvm::SelectionDAGISel::CodeGenAndEmitDAG() (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29d7feb) #19 0x029d7014 llvm::SelectionDAGISel::SelectAllBasicBlocks(llvm::Function const&) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29d7014) #20 0x029d6115 llvm::SelectionDAGISel::runOnMachineFunction(llvm::MachineFunction&) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x29d6115) #21 0x01dd3746 llvm::MachineFunctionPass::runOnFunction(llvm::Function&) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x1dd3746) #22 0x01fea56e llvm::FPPassManager::runOnFunction(llvm::Function&) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x1fea56e) #23 0x01fea973 llvm::FPPassManager::runOnModule(llvm::Module&) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x1fea973) #24 0x01fead6d (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x1fead6d) #25 0x01feab0d llvm::legacy::PassManagerImpl::run(llvm::Module&) (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x1feab0d) #26 0x0266a314 (/home/dhirvonen/Android/Sdk/ndk-bundle/toolchains/llvm/prebuilt/linux-x86_64/bin/clang+++0x266a314) #27 0x026679c2
[llvm-bugs] [Bug 40583] New: clang-format toggles between two different formattings
https://bugs.llvm.org/show_bug.cgi?id=40583 Bug ID: 40583 Summary: clang-format toggles between two different formattings Product: clang Version: 7.0 Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: Formatter Assignee: unassignedclangb...@nondot.org Reporter: fhoffm...@softwareparadies.de CC: djas...@google.com, kli...@google.com, llvm-bugs@lists.llvm.org Created attachment 21424 --> https://bugs.llvm.org/attachment.cgi?id=21424=edit minimized clang format files and source code examples Clang toggles between two different formattings in some special cases. This makes it impossible to use because there is no "correct" formatted code any more. example toggle1: < int maxH = ftoi((float)((aaa - ii) < / h)); // ii i aa.aa. i - --- > int maxH = > ftoi((float)((aaa - ii) > / h)); // ii i aa.aa. > i - I could not find one specific example which explains all the problems, so I have attached 4. My first Idea was that tabs are the only problem but then I discovered example 4, without any tabs. I hope the examples will help to find the bug. OS: Windows 10 clang-format version: 7.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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40582] New: Support -Wl, --no-insert-timestamp for MingW
https://bugs.llvm.org/show_bug.cgi?id=40582 Bug ID: 40582 Summary: Support -Wl,--no-insert-timestamp for MingW Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: g...@torproject.org CC: llvm-bugs@lists.llvm.org, mar...@martin.st, peter.sm...@linaro.org Created attachment 21423 --> https://bugs.llvm.org/attachment.cgi?id=21423=edit support -Wl,--no-insert-timestamp for MingW While preparing Tor Browser for the mingw-w64/clang toolchain I realized lld is not supporting ld's `-Wl,--no-insert-timestamp` option, which we used so far to deal with timestamps in PE headers. This functionality is available in COFF since https://reviews.llvm.org/rL332613 and I thought adding a few lines to make this available for MingW, too, would help us here. Attached is a patch that fixes this for MingW. -- 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 40581] New: Loop flattening not performed?
https://bugs.llvm.org/show_bug.cgi?id=40581
Bug ID: 40581
Summary: Loop flattening not performed?
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://godbolt.org/z/B3VM2A
void v0(int n, int *A, int *B) {
int k = 0;
for(int i = 0; i < n; i++)
for(int j = 0; j < n; j++) {
A[k] = B[k];
k++;
}
}
is equivalent to
void v1(int n, int *A, int *B) {
for(int i = 0; i < n; i++)
for(int j = 0; j < n; j++) {
int k = i*n+j;
A[k] = B[k];
k++;
}
}
(Also, which one of these ^ is better? clang does not optimize them into the
same IR)
Shouldn't that be transformed into
void v2(int n, int *A, int *B) {
for(int k = 0; k < n * n; k++)
A[k] = B[k];
}
?
--
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 40567] Merge r352889 into the 8.0 release branch
https://bugs.llvm.org/show_bug.cgi?id=40567 Hans Wennborg changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED CC||h...@chromium.org --- Comment #1 from Hans Wennborg --- Merged in r353029. Thanks! -- 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 40331] [meta] 8.0.0 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=40331 Bug 40331 depends on bug 40567, which changed state. Bug 40567 Summary: Merge r352889 into the 8.0 release branch https://bugs.llvm.org/show_bug.cgi?id=40567 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
