[llvm-bugs] [Bug 43902] New: clangd with compilation database and -stdlib=libc++
https://bugs.llvm.org/show_bug.cgi?id=43902 Bug ID: 43902 Summary: clangd with compilation database and -stdlib=libc++ Product: clang-tools-extra Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: clangd Assignee: unassignedclangb...@nondot.org Reporter: fredrik.slatt...@gmail.com CC: llvm-bugs@lists.llvm.org Created attachment 22768 --> https://bugs.llvm.org/attachment.cgi?id=22768&action=edit Output from both NeoVim and clangd when it fails When using clangd together with a compilation database which contains the compiler flag -stdlib=libc++ clangd fails to find system headers. I have created a git repo containing a reduced repro with logs that can be found here: https://github.com/fredrikslattman/clangd-libcpp. Development Environment: Ubuntu 18.0.4 LTS LLVM/Clang-9 installed through apt-get CMake 3.15 NeoVim 0.3.8 (with autozimu/LanguageClient 0.1.153) clangd is being invoked with the --compile-commands-dir= which picks up the correct compilation database. -- 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 18739 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
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 Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-11-05 Type: Bug New issue 18739 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::DiagnosticIDs::isUnrecoverable https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18739 Detailed Report: https://oss-fuzz.com/testcase?key=5718123382833152 Project: llvm Fuzzing Engine: libFuzzer Fuzz Target: clang-fuzzer Job Type: libfuzzer_asan_llvm Platform Id: linux Crash Type: Stack-overflow Crash Address: 0x7ffdc5891f58 Crash State: clang::DiagnosticIDs::isUnrecoverable clang::DiagnosticIDs::ProcessDiag clang::DiagnosticsEngine::EmitCurrentDiagnostic Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201911020345:201911030334 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5718123382833152 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 18568 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in llvm-opt-fuzzer--x86_64-strength_reduce
Updates: Labels: -Reproducible Unreproducible Comment #1 on issue 18568 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-strength_reduce: Timeout in llvm-opt-fuzzer--x86_64-strength_reduce https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18568#c1 ClusterFuzz testcase 5677977367216128 appears to be flaky, updating reproducibility label. -- 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 17969 in oss-fuzz: llvm:llvm-special-case-list-fuzzer: Timeout in llvm-special-case-list-fuzzer
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 17969 by ClusterFuzz-External: llvm:llvm-special-case-list-fuzzer: Timeout in llvm-special-case-list-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17969#c2 ClusterFuzz testcase 5656111637594112 appears to be flaky, updating reproducibility label. -- 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 18118 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm-opt-fuzzer--x86_64-indvars
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 18118 by ClusterFuzz-External: llvm:llvm-opt-fuzzer--x86_64-indvars: Timeout in llvm-opt-fuzzer--x86_64-indvars https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18118#c2 ClusterFuzz testcase 5652023936024576 appears to be flaky, updating reproducibility label. -- 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 43891] ARMCallingConv.cpp - unnecessary pass by (non-const) by reference
https://bugs.llvm.org/show_bug.cgi?id=43891 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Fixed By Commit(s)||rG73c3137a82c96789f4a2b8ec9 ||427d23fa73498d8 --- Comment #2 from Simon Pilgrim --- Thanks! Committed at rG73c3137a82c96789f4a2b8ec9427d23fa73498d8 -- 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 30996] [META] PVS Studio Warnings
https://bugs.llvm.org/show_bug.cgi?id=30996 Bug 30996 depends on bug 43891, which changed state. Bug 43891 Summary: ARMCallingConv.cpp - unnecessary pass by (non-const) by reference https://bugs.llvm.org/show_bug.cgi?id=43891 What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] Issue 17461 in oss-fuzz: llvm:llvm-isel-fuzzer--wasm32-O2: Timeout in llvm-isel-fuzzer--wasm32-O2
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 17461 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--wasm32-O2: Timeout in llvm-isel-fuzzer--wasm32-O2 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17461#c2 ClusterFuzz testcase 5645320205107200 appears to be flaky, updating reproducibility label. -- 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 17483 in oss-fuzz: llvm:clang-fuzzer: Timeout in clang-fuzzer
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 17483 by ClusterFuzz-External: llvm:clang-fuzzer: Timeout in clang-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17483#c2 ClusterFuzz testcase 5649598428741632 appears to be flaky, updating reproducibility label. -- 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 17808 in oss-fuzz: llvm:llvm-isel-fuzzer--x86_64-O2: Timeout in llvm-isel-fuzzer--x86_64-O2
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 17808 by ClusterFuzz-External: llvm:llvm-isel-fuzzer--x86_64-O2: Timeout in llvm-isel-fuzzer--x86_64-O2 https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=17808#c2 ClusterFuzz testcase 5644395369463808 appears to be flaky, updating reproducibility label. -- 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 18502 in oss-fuzz: llvm:clangd-fuzzer: Timeout in clangd-fuzzer
Updates: Labels: -Reproducible Unreproducible Comment #1 on issue 18502 by ClusterFuzz-External: llvm:clangd-fuzzer: Timeout in clangd-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18502#c1 ClusterFuzz testcase 5155469362724864 appears to be flaky, updating reproducibility label. -- 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 18446 in oss-fuzz: llvm:clang-objc-fuzzer: Timeout in clang-objc-fuzzer
Updates: Labels: -Reproducible Unreproducible Comment #2 on issue 18446 by ClusterFuzz-External: llvm:clang-objc-fuzzer: Timeout in clang-objc-fuzzer https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18446#c2 ClusterFuzz testcase 5728496516595712 appears to be flaky, updating reproducibility label. -- 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 43282] Preprocessor bug/incompatibility regarding __VA_ARGS__ and comma when compiling with -fms-compatibility on Windows
https://bugs.llvm.org/show_bug.cgi?id=43282 Eric Astor changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 38780] [DebugInfo@O2
https://bugs.llvm.org/show_bug.cgi?id=38780 J. Ryan Stinnett changed: What|Removed |Added CC||jry...@gmail.com Resolution|FIXED |INVALID -- 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 43900] New: Memory Corruption with clang-cl
https://bugs.llvm.org/show_bug.cgi?id=43900
Bug ID: 43900
Summary: Memory Corruption with clang-cl
Product: clang
Version: 9.0
Hardware: PC
OS: other
Status: NEW
Severity: normal
Priority: P
Component: C++
Assignee: unassignedclangb...@nondot.org
Reporter: bussyanto...@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 22766
--> https://bugs.llvm.org/attachment.cgi?id=22766&action=edit
Reproduction of bug
Hi,
I've encountered a weird bug when using args (https://github.com/Taywee/args)
with clang-cl on Windows 10, in release mode only. Using Visual Studio 2019
debugger, I suspect a memory corruption. Here is the code:
#include "args.hpp"
#include
inline auto to_argv(std::vector& v)
{
auto r = std::vector{};
for (auto& e : v)
r.emplace_back(e.data());
r.emplace_back(nullptr);
return r;
}
auto other_main(int argc, char* argv[]) -> int
{
std::cerr << argc << std::endl;
for(auto i = 0; i < argc; ++i)
std::cerr << argv[i] << std::endl;
auto parser = args::ArgumentParser{ "Command Line" };
auto const help = args::HelpFlag{ parser, "help", "Display this help
menu", {'h', "help"} };
try
{
parser.ParseCLI(argc, argv);
}
catch (const args::Help&)
{
}
return 0;
}
int main(int argc, char* argv[])
{
auto const commands = std::vector
{
"command",
"command_2",
};
for (auto const& command : commands)
{
auto _args = std::vector
{
command,
"-h",
};
for (auto const& a : _args)
std::cerr << a << std::endl;
auto args = to_argv(_args);
other_main(static_cast(args.size()) - 1, args.data());
}
}
This should print:
command
-h
2
command
-h
command_2
-h
2
command_2
-h
which it does in debug (or with MSVC or clang on Linux), but it prints:
command
-h
2
command
-h
command_2
2
command_2
-h
In other cases I tested, it prints rubbish, or simply crashes. I attached the
whole self-contained sample, with example cmake commands.
--
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 43899] New: Incomplete optimization during loop vectorization on large arrays.
https://bugs.llvm.org/show_bug.cgi?id=43899
Bug ID: 43899
Summary: Incomplete optimization during loop vectorization on
large arrays.
Product: libraries
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: enhancement
Priority: P
Component: Loop Optimizer
Assignee: unassignedb...@nondot.org
Reporter: a.rain...@gmail.com
CC: llvm-bugs@lists.llvm.org
I use x86-64 trunk or 9.0 version with -Ofast
The example functions creates different code for same array and loop size, this
is a bug because loops are identical.
For comparsion asm codes I create the example: https://godbolt.org/z/YgKRZO
#include
#include
#include
typedef
int64_t
my_c_arr[1024 * 1024 * 1024];
typedef
std::array
my_arr;
void compute_1(my_c_arr& input)
{
for (auto i: input)
{
input[i] = (input[i] + 3254) * 3;
}
}
void compute_2(my_arr& input)
{
for (auto i: input)
{
input[i] = (input[i] + 3254) * 3;
}
}
void compute_3(my_arr& input)
{
for (auto i = input.begin(); i != input.cend(); ++i)
{
*i = (*i + 3254) * 3;
}
}
all compute_1... creates asm:
compute_1(long (&) [1073741824]): # @compute_1(long (&) [1073741824])
movabs rax, 8589934592
add rax, rdi
mov rcx, rdi
.LBB0_1:# =>This Inner Loop Header: Depth=1
mov rdx, qword ptr [rcx]
mov rsi, qword ptr [rdi + 8*rdx]
lea rsi, [rsi + 2*rsi]
add rsi, 9762
mov qword ptr [rdi + 8*rdx], rsi
mov rdx, qword ptr [rcx + 8]
mov rsi, qword ptr [rdi + 8*rdx]
lea rsi, [rsi + 2*rsi + 9762]
mov qword ptr [rdi + 8*rdx], rsi
mov rdx, qword ptr [rcx + 16]
mov rsi, qword ptr [rdi + 8*rdx]
lea rsi, [rsi + 2*rsi + 9762]
mov qword ptr [rdi + 8*rdx], rsi
mov rdx, qword ptr [rcx + 24]
mov rsi, qword ptr [rdi + 8*rdx]
lea rsi, [rsi + 2*rsi]
add rsi, 9762
mov qword ptr [rdi + 8*rdx], rsi
add rcx, 32
cmp rcx, rax
jne .LBB0_1
ret
void compute_10(my_c_arr& input)
{
for (auto i = 0; i != sizeof(input) / sizeof(input[0]); ++i)
{
input[i] = (input[i] + 3254) * 3;
}
}
void compute_11(my_arr& input)
{
for (auto i = 0; i != input.size(); ++i)
{
input[i] = (input[i] + 3254) * 3;
}
}
all of compute_1*... creates this asm code:
compute_10(long (&) [1073741824]): # @compute_10(long (&) [1073741824])
xor eax, eax
.LBB0_1:# =>This Inner Loop Header: Depth=1
mov rcx, qword ptr [rdi + 8*rax]
mov rdx, qword ptr [rdi + 8*rax + 8]
lea rcx, [rcx + 2*rcx]
add rcx, 9762
mov qword ptr [rdi + 8*rax], rcx
lea rcx, [rdx + 2*rdx + 9762]
mov qword ptr [rdi + 8*rax + 8], rcx
mov rcx, qword ptr [rdi + 8*rax + 16]
lea rcx, [rcx + 2*rcx + 9762]
mov qword ptr [rdi + 8*rax + 16], rcx
mov rcx, qword ptr [rdi + 8*rax + 24]
lea rcx, [rcx + 2*rcx]
add rcx, 9762
mov qword ptr [rdi + 8*rax + 24], rcx
add rax, 4
cmp rax, 1073741824
jne .LBB0_1
ret
--
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 43799] slp-vectorizer crashes: Assertion `Elt->getType() == Val->getType()->getVectorElementType() && "Insertelement types must match!"' failed.
https://bugs.llvm.org/show_bug.cgi?id=43799 Alexey Bataev changed: What|Removed |Added Status|CONFIRMED |RESOLVED Fixed By Commit(s)||b80c41cd3c095c8c4fa739130b5 ||60b15bda4bbd0 Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 43898] New: [PeepholeOptimizer] foldRedundantCopy breaks if Copy is changed by TII.foldImmediate
https://bugs.llvm.org/show_bug.cgi?id=43898 Bug ID: 43898 Summary: [PeepholeOptimizer] foldRedundantCopy breaks if Copy is changed by TII.foldImmediate Product: libraries Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: enhancement Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: alex.dav...@iinet.net.au CC: llvm-bugs@lists.llvm.org For all MIs per basic block: foldRedundantCopy tracks copy instructions and places them in DenseMap CopyMIs. foldImmediate tracks isMoveImm, and calls foldImmediate on uses of these. foldImmediate is allowed to change the desc of UseMI - see ARMBaseInstrInfo.cpp. On seeing the description for "foldImmediate", it seems logical to optimize copy instructions - but if you try to do so, it's only a matter of time until compilation fails, as foldRedundantCopy does not verify that instructions in CopyMI is still actually a copy instruction. I figure either (1) do not call foldImmediate on COPYs, if it is recommended that targets do not perform this optimization here, or (2) add: if (!PrevCopy->isCopy()) return false; to line 1410 of PeepholeOptimizer.cpp Cheers :) -- 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 43897] New: LLVM should not remove branches if not profitable
https://bugs.llvm.org/show_bug.cgi?id=43897
Bug ID: 43897
Summary: LLVM should not remove branches if not profitable
Product: libraries
Version: trunk
Hardware: PC
OS: Linux
Status: NEW
Severity: enhancement
Priority: P
Component: Scalar Optimizations
Assignee: unassignedb...@nondot.org
Reporter: david.bolvan...@gmail.com
CC: llvm-bugs@lists.llvm.org
void foo(char **d, char **s, int n, int m) {
for (int i = 0; i < n; ++i) {
if (m == 128) // m is usually 128, hot path
__builtin_memcpy(d[i], s[i], m);
else
__builtin_memcpy(d[i], s[i], m);
}
}
LLVM (Simplify CFG?) removes branch and leaves '__builtin_memcpy(d[i], s[i],
m);'. But here, LLVM was too smart and ignored what I wanted to do - "inlined"
version of memcpy.
If I use:
if (m == 128)
__builtin_memcpy(d[i], s[i], 128);
else
__builtin_memcpy(d[i], s[i], m);
Everything is OK. Simplify CFG should not merge branches if it can propagate
constant from condition to one branch.
https://godbolt.org/z/GFfPrb
--
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 43896] New: Implement ISO/IEC JTC1 SC22 WG14 N1169 fixed-point types and arithmetic
https://bugs.llvm.org/show_bug.cgi?id=43896 Bug ID: 43896 Summary: Implement ISO/IEC JTC1 SC22 WG14 N1169 fixed-point types and arithmetic Product: clang Version: trunk Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Frontend Assignee: unassignedclangb...@nondot.org Reporter: bevin.hans...@ericsson.com CC: llvm-bugs@lists.llvm.org, neeil...@live.com, richard-l...@metafoo.co.uk This is a ticket to track the remaining work required for supporting the ISO/IEC JTC1 SC22 WG14 N1169 fixed-point types and arithmetic. Although this ticket is filed under Clang Frontend, the remaining work also includes patches to LLVM and other parts of Clang. The currently estimated work that remains is: LLVM: * Intrinsic for fixed-point [saturating] division * Possibly intrinsics for floating point/fixed-point conversion * Possibly intrinsic for saturating left shift Clang: * Precision/limits macros (stdfix.h) * Constant evaluation ** Subtraction ** Multiplication ** Division ** Shift ** Floating point conversion * Compound assignment * Codegen ** Multiplication ** Division ** Shift ** Unary operations ** Floating point conversion -- 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 43024] Compile-time regression after r368307
https://bugs.llvm.org/show_bug.cgi?id=43024 Simon Pilgrim changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|rG3f087e38a2e7b87a5adaaac1c |rG3f087e38a2e7b87a5adaaac1c |1b61e51220e7ff3 |1b61e51220e7ff3, ||rG31ed36d0447def348af7b1d27 ||daceb57d063382f Status|CONFIRMED |RESOLVED --- Comment #4 from Simon Pilgrim --- Reapplied in rG31ed36d0447def348af7b1d27daceb57d063382f -- 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 43877] Add packages for Ubuntu 19.10 Eoan Ermine
https://bugs.llvm.org/show_bug.cgi?id=43877 Sylvestre Ledru changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Sylvestre Ledru --- I updated the website. Should be live soon (cdn delay) -- 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 43679] [LoopDataPrefetch] Creates prefetch 3.5 terabytes ahead
https://bugs.llvm.org/show_bug.cgi?id=43679 Jonas Paulsson changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #11 from Jonas Paulsson --- The SystemZ backend has now been improved per Elis suggestions (580310f), so I am closing 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 https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
