[llvm-bugs] [Bug 44141] openmp libomptarget tests fail on trunk
https://bugs.llvm.org/show_bug.cgi?id=44141 Bryan Chan changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #10 from Bryan Chan --- D70803 has landed. -- 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 43418] The linker can't find matching R_RISCV_PCREF_HI20 to the R_RISCV_PCREF_LO12
https://bugs.llvm.org/show_bug.cgi?id=43418 Fangrui Song changed: What|Removed |Added CC||i...@maskray.me Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Fangrui Song --- I think the patch is based on lld 8.0 . The deleted lines were introduced in https://reviews.llvm.org/D39322 (2018-08) and were actually changed in 2019-02. lld 8 does not have complete RISC-V support, notably it lacks PLT/GOT/TLS. lld 9 has relative complete support (it still lacks relaxation This particular problem has been fixed for a while, maybe by https://reviews.llvm.org/D63123 (2019-06-11) -- 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 42541] PowerPC integrated as - missing instructions mulldo, addo and subfo
https://bugs.llvm.org/show_bug.cgi?id=42541 Kamau Bridgeman changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #9 from Kamau Bridgeman --- (In reply to Tom Stellard from comment #7) > So this change is required in order to build GHC? > > Hal, what do you think about backporting this? Hi Tom, I'm pinging this bug to make sure it makes it into rc2. Do our have plans to merge it in? -- 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 43360] [meta] 9.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=43360 Bug 43360 depends on bug 42541, which changed state. Bug 42541 Summary: PowerPC integrated as - missing instructions mulldo, addo and subfo https://bugs.llvm.org/show_bug.cgi?id=42541 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] Issue 19182 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::ActOnTag
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.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 Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2019-11-29 Type: Bug-Security New issue 19182 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::ActOnTag https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19182 Detailed Report: https://oss-fuzz.com/testcase?key=5715582179868672 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Segv on unknown address Crash Address: Crash State: clang::Sema::ActOnTag clang::Parser::ParseEnumSpecifier clang::Parser::ParseDeclarationSpecifiers Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=201911200438:201911230451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5715582179868672 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing 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. Comments on individual Monorail issues are not monitored. -- 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 19181 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::LookupQualifiedName
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.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 Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2019-11-29 Type: Bug-Security New issue 19181 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in clang::Sema::LookupQualifiedName https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19181 Detailed Report: https://oss-fuzz.com/testcase?key=5702033537761280 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Segv on unknown address Crash Address: Crash State: clang::Sema::LookupQualifiedName clang::Sema::CppLookupName clang::Sema::LookupName Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=201911200438:201911230451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5702033537761280 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing 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. Comments on individual Monorail issues are not monitored. -- 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 19180 in oss-fuzz: llvm:clang-fuzzer: Segv on unknown address in llvm::APInt::udiv
Status: New Owner: CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, d...@google.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 Reproducible Stability-Memory-MemorySanitizer Engine-libfuzzer OS-Linux Proj-llvm Security_Severity-High Reported-2019-11-29 Type: Bug-Security New issue 19180 by ClusterFuzz-External: llvm:clang-fuzzer: Segv on unknown address in llvm::APInt::udiv https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=19180 Detailed Report: https://oss-fuzz.com/testcase?key=5698461165158400 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_msan_llvm Platform Id: linux Crash Type: Segv on unknown address Crash Address: Crash State: llvm::APInt::udiv ComplexExprEvaluator::VisitBinaryOperator clang::StmtVisitorBasebool>::Visit Sanitizer: memory (MSAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&range=201911200438:201911230451 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5698461165158400 Issue filed automatically. See https://google.github.io/oss-fuzz/advanced-topics/reproducing 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. Comments on individual Monorail issues are not monitored. -- 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 25602] Inliner generates 'bitcast' instead of 'addrspacecast'
https://bugs.llvm.org/show_bug.cgi?id=25602 Ehud Katz changed: What|Removed |Added Resolution|--- |FIXED CC||ehudk...@gmail.com Status|NEW |RESOLVED --- Comment #1 from Ehud Katz --- Fixed in LLVM v7.0. -- 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 44184] New: ICE in ActOnCapScopeReturnStmt when default argument contains statement-expression
https://bugs.llvm.org/show_bug.cgi?id=44184
Bug ID: 44184
Summary: ICE in ActOnCapScopeReturnStmt when default argument
contains statement-expression
Product: clang
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: arthur.j.odw...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
// https://godbolt.org/z/VE-Zk4
int test1() {
[](int = ({return 42; 0;}) ) {};
return 17;
}
int test2() {
[](decltype( ({return 42; 0;}) )) {}(0);
return 17;
}
GCC compiles these function into the equivalent of "return 42" and "return 17"
respectively.
Intel ICC rejects the first function with "error: a statement expression is not
allowed inside of a default argument", and ICEs with "bad pointer" on the
second function.
Clang ICEs on both functions. I think it would be reasonable for Clang to
follow Intel ICC and give a hard error on any attempt to abuse
statement-expressions like this; but Clang still shouldn't ICE.
Stack dump:
0. Program arguments:
/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10 -cc1 -triple
x86_64-unknown-linux-gnu -S -disable-free -disable-llvm-verifier
-discard-value-names -main-file-name example.cpp -mrelocation-model static
-mthread-model posix -mframe-pointer=all -fmath-errno -masm-verbose
-mconstructor-aliases -munwind-tables -fuse-init-array -target-cpu x86-64
-dwarf-column-info -debug-info-kind=limited -dwarf-version=4
-debugger-tuning=gdb -resource-dir
/opt/compiler-explorer/clang-trunk-20191129/lib/clang/10.0.0 -internal-isystem
/opt/compiler-explorer/gcc-9.2.0/lib/gcc/x86_64-linux-gnu/9.2.0/../../../../include/c++/9.2.0
-internal-isystem
/opt/compiler-explorer/gcc-9.2.0/lib/gcc/x86_64-linux-gnu/9.2.0/../../../../include/c++/9.2.0/x86_64-linux-gnu
-internal-isystem
/opt/compiler-explorer/gcc-9.2.0/lib/gcc/x86_64-linux-gnu/9.2.0/../../../../include/c++/9.2.0/backward
-internal-isystem /usr/local/include -internal-isystem
/opt/compiler-explorer/clang-trunk-20191129/lib/clang/10.0.0/include
-internal-externc-isystem /usr/include/x86_64-linux-gnu
-internal-externc-isystem /include -internal-externc-isystem /usr/include
-std=c++2a -fdeprecated-macro -fdebug-compilation-dir /home/ubuntu
-ferror-limit 19 -fmessage-length 0 -fgnuc-version=4.2.1 -fno-implicit-modules
-fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option
-fcolor-diagnostics -faddrsig -o ./output.s -x c++
1. :3:22: current parser token ';'
2. :2:13: parsing function body 'test'
3. :2:13: in compound statement ('{}')
4. :3:5: lambda expression parsing
5. :3:15: in compound statement ('{}')
#0 0x555af942f0fa llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x29580fa)
#1 0x0000555af942ce14 llvm::sys::RunSignalHandlers()
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x2955e14)
#2 0x555af942cf52 SignalHandler(int)
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x2955f52)
#3 0x7faa0cd95890 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x12890)
#4 0x555afafd400f
clang::Sema::ActOnCapScopeReturnStmt(clang::SourceLocation, clang::Expr*)
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x44fd00f)
#5 0x555afafd49b7 clang::Sema::BuildReturnStmt(clang::SourceLocation,
clang::Expr*)
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x44fd9b7)
#6 0x555afafd535a clang::Sema::ActOnReturnStmt(clang::SourceLocation,
clang::Expr*, clang::Scope*)
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x44fe35a)
#7 0x0000555afaae6c45 clang::Parser::ParseReturnStatement()
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x400fc45)
#8 0x555afaaebbef
clang::Parser::ParseStatementOrDeclarationAfterAttributes(llvm::SmallVector&, clang::Parser::ParsedStmtContext, clang::SourceLocation*,
clang::Parser::ParsedAttributesWithRange&)
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x4014bef)
#9 0x555afaaed6e9
clang::Parser::ParseStatementOrDeclaration(llvm::SmallVector&, clang::Parser::ParsedStmtContext, clang::SourceLocation*)
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x40166e9)
#10 0x555afaae86d1 clang::Parser::ParseCompoundStatementBody(bool)
(/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x40116d1)
#11 0x555afaae8f4e clang::Parser::ParseCompoundStatement(bool, unsigned
int) (/opt/compiler-explorer/clang-trunk-20191129/bin/clang-10+0x4011f4e)
#12 0x555afaaa4a3a
clang::Parser::ParseParenExpression(clang::Parser::ParenParseOption&, bool,
b
[llvm-bugs] [Bug 44183] New: Clang 9 abort trap when building mesa drivers on FreeBSD
https://bugs.llvm.org/show_bug.cgi?id=44183 Bug ID: 44183 Summary: Clang 9 abort trap when building mesa drivers on FreeBSD Product: libraries Version: 9.0 Hardware: PC OS: FreeBSD Status: NEW Severity: enhancement Priority: P Component: Backend: PowerPC Assignee: unassignedb...@nondot.org Reporter: alfredo.jun...@eldorado.org.br CC: llvm-bugs@lists.llvm.org, nemanja.i@gmail.com Created attachment 22882 --> https://bugs.llvm.org/attachment.cgi?id=22882&action=edit Preoprocessed source and associated run script I hit the following Abort when building package ports/graphics/mesa-dri on FreeBSD/powerpc64 ELFv2 ABI. Please let me know if you need more info. Thanks!! 1. parser at end of file 2. Code generation 3. Running pass 'Function Pass Manager' on module 'sb/sb_bc_builder.cpp'. 4. Running pass 'Linux PPC Assembly Printer' on function '@_ZN7r600_sb10bc_builder8build_cfEPNS_7cf_nodeE' #0 0x1371670c (/usr/bin/c+++0x1371670c) #1 0x13716d88 (/usr/bin/c+++0x13716d88) #2 0x1371404c (/usr/bin/c+++0x1371404c) #3 0x13717500 (/usr/bin/c+++0x13717500) #4 0x0008151f176c (/lib/libthr.so.3+0x1b76c) c++: error: unable to execute command: Abort trap (core dumped) c++: error: clang frontend command failed due to signal (use -v to see invocation) FreeBSD clang version 9.0.0 (tags/RELEASE_900/final 372316) (based on LLVM 9.0.0) Target: powerpc64-unknown-freebsd13.0 Thread model: posix InstalledDir: /usr/bin c++: note: diagnostic msg: PLEASE submit a bug report to https://bugs.freebsd.org/submit/ and include the crash backtrace, preprocessed source, and associated run script. c++: note: diagnostic msg: PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT: Preprocessed source(s) and associated run script(s) are located at: c++: note: diagnostic msg: /tmp/sb_bc_builder-3d0404.cpp c++: note: diagnostic msg: /tmp/sb_bc_builder-3d0404.sh c++: note: diagnostic msg: -- 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 17049 in oss-fuzz: llvm:llvm-itanium-demangle-fuzzer: ASSERT: Parser->TemplateParams.size() >= OldNumTemplateParamLists
Updates: Labels: Deadline-Approaching Comment #2 on issue 17049 by sheriff...@chromium.org: llvm:llvm-itanium-demangle-fuzzer: ASSERT: Parser->TemplateParams.size() >= OldNumTemplateParamLists https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17049#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 44182] New: 'The dependency target "cxx" of target "check-cxxabi" does not exist.'
https://bugs.llvm.org/show_bug.cgi?id=44182 Bug ID: 44182 Summary: 'The dependency target "cxx" of target "check-cxxabi" does not exist.' Product: Build scripts Version: trunk Hardware: Macintosh OS: MacOS X Status: NEW Severity: enhancement Priority: P Component: cmake Assignee: unassignedb...@nondot.org Reporter: arthur.j.odw...@gmail.com CC: llvm-bugs@lists.llvm.org While trying to solve another problem (related to build failures in the "cxx" target), I tried making a build that enabled *only* the "clang" and "libcxxabi" projects (but not the "libcxx" project). This fails with a CMake error. Ideally, it would either Just Work (by auto-enabling all dependencies of every enabled project), or give a customized and helpful error message (e.g. "you can't build libcxxabi alone; please add 'libcxx' to LLVM_ENABLE_PROJECTS and try again"). Here's the current output: $ cmake -G 'Ninja' -DLLVM_ENABLE_PROJECTS="clang;libcxxabi" -DCMAKE_BUILD_TYPE=RelWithDebInfo ../llvm [...] -- Configuring done CMake Error at cmake/modules/AddLLVM.cmake:1456 (add_dependencies): The dependency target "cxx" of target "check-all" does not exist. Call Stack (most recent call first): CMakeLists.txt:991 (add_lit_target) CMake Error at /tmp/llvm-project/llvm/cmake/modules/AddLLVM.cmake:1456 (add_dependencies): The dependency target "cxx" of target "check-cxxabi" does not exist. Call Stack (most recent call first): /tmp/llvm-project/llvm/cmake/modules/AddLLVM.cmake:1477 (add_lit_target) /tmp/llvm-project/libcxxabi/test/CMakeLists.txt:52 (add_lit_testsuite) -- Generating done -- Build files have been written to: /tmp/llvm-project/build This is on OS X High Sierra 10.13.6, with a native toolchain of $ clang --version Apple LLVM version 7.3.0 (clang-703.0.31) Target: x86_64-apple-darwin17.7.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin $ cmake --version cmake version 3.12.0 CMake suite maintained and supported by Kitware (kitware.com/cmake). -- 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 43945] Loop Vectorization pass segfaults.
https://bugs.llvm.org/show_bug.cgi?id=43945 Florian Hahn changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #2 from Florian Hahn --- I cannot reproduce the crash with current trunk. IIRC there was an issue causing a vectorizer crash, which was fixed in the meantime. Please feel free to re-open with a new reproducer, if the problem still exists. -- 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 43951] [LoopVectorizer] Assertion `Instance.Lane > 0 ? !Cost->isUniformAfterVectorization(cast(V), VF) : true && "Uniform values only have lane zero"' failed.
https://bugs.llvm.org/show_bug.cgi?id=43951 Florian Hahn changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEW |RESOLVED --- Comment #1 from Florian Hahn --- I think this is a duplicate of https://bugs.llvm.org/show_bug.cgi?id=40816 The proposed patch there fixes the crash for the reproducer attached here. *** This bug has been marked as a duplicate of bug 40816 *** -- 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 44054] [ImplicitConversionSaitizer] Missing overflow check for ++x compared to x += 1
https://bugs.llvm.org/show_bug.cgi?id=44054 Roman Lebedev changed: What|Removed |Added Resolution|--- |FIXED Status|REOPENED|RESOLVED Fixed By Commit(s)|9872ea4ed1de4c49300430e4f1f |9872ea4ed1de4c49300430e4f1f |4dfc110a79ab9 |4dfc110a79ab9, ||b98a0c7f6c9c7b38b6cd764e6f4 ||7e16e3d8c342c --- Comment #7 from Roman Lebedev --- Relanded in b98a0c7f6c9c7b38b6cd764e6f47e16e3d8c342c, seems to be good so far. -- 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 43425] -fprofile-generate profile merging from concurrent processes fails on Windows with "LLVM Profile Error: Failed to write file ... File exists"
https://bugs.llvm.org/show_bug.cgi?id=43425 Hans Wennborg changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #4 from Hans Wennborg --- Should be fixed by Michael's https://reviews.llvm.org/D70330 -- 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 44181] New: Quoting style when expanding response file
https://bugs.llvm.org/show_bug.cgi?id=44181 Bug ID: 44181 Summary: Quoting style when expanding response file Product: lld Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: wasm Assignee: unassignedb...@nondot.org Reporter: eric.pelliss...@sivilog.com CC: llvm-bugs@lists.llvm.org, s...@chromium.org When using wasm-ld from Visual Studio, the response file provided to the linker uses the Windows quoting style instead of the GNU one. Unfortunately the current version of wasm-ld always uses the "cl::TokenizeGNUCommandLine" when expanding the response file. It would be good to use the same trick as in the MinGW version of Driver.cpp with a "getDefaultQuotingStyle()" function that returns either "cl::TokenizeGNUCommandLine" or "cl::TokenizeWindowsCommandLine" depending on the triple (see Diff 203886). I have implemented this locally and can provide a patch if needed. Thanks a lot. -- 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 44180] New: TestShowLocationDwarf5.py fails on AArch64 Ubuntu
https://bugs.llvm.org/show_bug.cgi?id=44180
Bug ID: 44180
Summary: TestShowLocationDwarf5.py fails on AArch64 Ubuntu
Product: lldb
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: All Bugs
Assignee: lldb-...@lists.llvm.org
Reporter: diana.pi...@linaro.org
CC: jdevliegh...@apple.com, llvm-bugs@lists.llvm.org
ERROR: test_source_map_dwo (TestShowLocationDwarf5.TestTargetSourceMap)
--
Traceback (most recent call last):
File
"/home/diana.picus/llvm-envs/lldb/llvm/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 1851, in setUp
Base.setUp(self)
File
"/home/diana.picus/llvm-envs/lldb/llvm/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 825, in setUp
self.darwinWithFramework = self.platformIsDarwin()
File
"/home/diana.picus/llvm-envs/lldb/llvm/lldb/packages/Python/lldbsuite/test/lldbtest.py",
line 1299, in platformIsDarwin
return lldbplatformutil.platformIsDarwin()
File
"/home/diana.picus/llvm-envs/lldb/llvm/lldb/packages/Python/lldbsuite/test/lldbplatformutil.py",
line 142, in platformIsDarwin
return getPlatform() in getDarwinOSTriples()
File
"/home/diana.picus/llvm-envs/lldb/llvm/lldb/packages/Python/lldbsuite/test/lldbplatformutil.py",
line 132, in getPlatform
platform = lldb.DBG.GetSelectedPlatform().GetTriple().split('-')[2]
AttributeError: 'NoneType' object has no attribute 'split'
Config=aarch64-/home/diana.picus/llvm-envs/lldb/build/bin/clang-10
Strangely enough, this only happens for dwo (dwarf passes).
--
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 44179] New: llvm-config --system-libs prints entire libxml2 path
https://bugs.llvm.org/show_bug.cgi?id=44179 Bug ID: 44179 Summary: llvm-config --system-libs prints entire libxml2 path Product: new-bugs Version: trunk Hardware: PC OS: All Status: NEW Keywords: regression Severity: enhancement Priority: P Component: new bugs Assignee: unassignedb...@nondot.org Reporter: v...@freedesktop.org CC: compn...@compnerd.org, htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org llvm-config --system-libs now prints the entire libxml2 path. Before $ llvm-config --system-libs -lz -lrt -ldl -ltinfo -lpthread -lm -lxml2 Now $ llvm-config --system-libs -lz -lrt -ldl -ltinfo -lpthread -lm -l/usr/lib/x86_64-linux-gnu/libxml2.so This leads to linking errors if depending on llvm-config --system-libs during compilation. /usr/bin/ld: cannot find -l/usr/lib/x86_64-linux-gnu/libxml2 This new behavior is introduced with these llvm-10 commits. commit cfcfd8a056eb7c01bc76b745ce9f7839f0dcbc42 Author: Saleem Abdulrasool Date: Wed Nov 27 12:55:46 2019 -0800 build: avoid cached literals being linked against If the value of the LibXml2 search is cached, it can cause an errant link against LIBXML2_LIBRARIES-NOTFOUND if libxml2 is not found. Add a guard against this. Should repair the build bots. commit 340e7c0b77a7037afefe7255503afe362967b577 Author: Saleem Abdulrasool Date: Wed Nov 27 12:34:36 2019 -0800 build: avoid hardcoding the libxml2 library name FindLibXml2 will set the LIBXML2_LIBRARIES variable to the libraries that we must link against. This will be an empty string if libxml2 is not found. Avoid hardcoding the library name as xml2 in the configuration. Simplify the usage in the WindowsManifest library. -- 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
