[llvm-bugs] [Bug 41863] [C++17] std:variant fails with libstdc++ from gcc-9.1.0
https://bugs.llvm.org/show_bug.cgi?id=41863 Hunter Sezen changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #6 from Hunter Sezen --- Ah, thanks for pointing out the libstdc++ fix, I guess that effectively solves this and I'll mark this as fixed. I don't think there is anything more that can be done here? -- 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 41673] /DISCARD/ section should not be output
https://bugs.llvm.org/show_bug.cgi?id=41673 Andrew Ng changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #2 from Andrew Ng --- D61186 was to fix the issue that /DISCARD/ sections were being treated as orphans and as a result, could cause unwanted side-effects. D61186 does not fix the problem that an empty /DISCARD/ section can be retained in the output in certain circumstances. This is not a correctness issue, but is not ideal. -- 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 41817] The linkage changes in r359260 break MIDL code
https://bugs.llvm.org/show_bug.cgi?id=41817 Hans Wennborg changed: What|Removed |Added Status|RESOLVED|REOPENED CC||h...@chromium.org Resolution|FIXED |--- --- Comment #3 from Hans Wennborg --- (In reply to Richard Smith from comment #2) > Should be fixed in r360637. I had to revert that in r360657 because it broke Chromium, see http://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20190513/271324.htm -- 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 4012] The clang web page needs to be improved (& looks atrocious in IE 6.0)
https://bugs.llvm.org/show_bug.cgi?id=4012 J. Ryan Stinnett changed: What|Removed |Added Status|NEW |RESOLVED CC||jry...@gmail.com Resolution|--- |WORKSFORME --- Comment #5 from J. Ryan Stinnett --- I think we can consider this resolved now. clang.llvm.org looks usable at large and small widths on both desktop and mobile browsers. I am sure various things could still be improved, but it's probably best to file separate issues with detail about each suggestion. -- 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 41869] New: [DebugInfo] DbgEntityHistoryCalculator assumes "last" block is exit block
https://bugs.llvm.org/show_bug.cgi?id=41869 Bug ID: 41869 Summary: [DebugInfo] DbgEntityHistoryCalculator assumes "last" block is exit block Product: libraries Version: trunk Hardware: PC OS: Linux Status: NEW Keywords: wrong-debug Severity: normal Priority: P Component: Common Code Generator Code Assignee: unassignedb...@nondot.org Reporter: jeremy.morse.l...@gmail.com CC: chackz0...@gmail.com, david.stenb...@ericsson.com, greg.bedw...@sony.com, llvm-bugs@lists.llvm.org, orlando.hy...@sony.com, paul.robin...@am.sony.com, stephen.to...@sony.com As it stands, DbgEntityHistoryCalculator currently makes the assumption [0] that the last (by order) basic block in a function is the exit block. This sometimes isn't true, for various reasons (block layout, PGO, tail duplication etc) and yet "open ended" debug locations are something that other parts of DwarfDebug rely on, for example the validThroughout function. This probably isn't a high priority item given other debuginfo problems; but something that should eventually be addressed. [0] https://github.com/llvm/llvm-project/blob/c93f56d39e629b7bcd0f4657705264fcd7e47c0d/llvm/lib/CodeGen/AsmPrinter/DbgEntityHistoryCalculator.cpp#L355 -- 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 41871] New: --source does not work with archive members
https://bugs.llvm.org/show_bug.cgi?id=41871 Bug ID: 41871 Summary: --source does not work with archive members Product: tools Version: trunk Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P Component: llvm-objdump Assignee: unassignedb...@nondot.org Reporter: jh7370.2...@my.bristol.ac.uk CC: llvm-bugs@lists.llvm.org It is possible for an archive to contain members with debug data in, and it should be possible to use --source to emit the source information of such members inline with their disassembly (GNU does). However, this does not work in llvm-objdump. This is because it tries to symbolize based on the member name, which in turn tries to find an object on disk with that name, which will often not exist. -- 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 14731 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Comment #1 on issue 14731 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14731#c1 ClusterFuzz has detected this issue as fixed in range 201905130305:201905132004. Detailed report: https://oss-fuzz.com/testcase?key=5702736739303424 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: 0x7ffeec54be68 Crash State: GetFullTypeForDeclarator clang::Sema::GetTypeForDeclarator clang::Sema::ActOnBlockArguments Sanitizer: address (ASAN) Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201905090310:201905100308 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201905130305:201905132004 Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=5702736739303424 See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for instructions to reproduce this bug locally. If you suspect that the result above is incorrect, try re-doing that job on the test case report page. -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41872] New: Merge r359569 into the 8.0 branch
https://bugs.llvm.org/show_bug.cgi?id=41872 Bug ID: 41872 Summary: Merge r359569 into the 8.0 branch 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: russell_gal...@sn.scee.net CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org This is required for people to using PGO from the Windows release package. -- 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 41873] New: Merge r360674 into 8.0
https://bugs.llvm.org/show_bug.cgi?id=41873 Bug ID: 41873 Summary: Merge r360674 into 8.0 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: russell_gal...@sn.scee.net CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org This is a quality of life improvement for using PGO on Windows, and helps with self hosting LLVM with PGO. -- 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 14731 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator
Updates: Labels: ClusterFuzz-Verified Status: Verified Comment #2 on issue 14731 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow in GetFullTypeForDeclarator https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=14731#c2 ClusterFuzz testcase 5702736739303424 is verified as fixed, so closing issue as verified. If this is incorrect, please file a bug on https://github.com/google/oss-fuzz/issues/new -- You received this message because: 1. You were specifically CC'd on the issue You may adjust your notification preferences at: https://bugs.chromium.org/hosting/settings Reply to this email to add a comment. ___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41874] New: [DAGCombine] Combine constant and+shift --> shift+shift
https://bugs.llvm.org/show_bug.cgi?id=41874 Bug ID: 41874 Summary: [DAGCombine] Combine constant and+shift --> shift+shift 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: llvm-...@redking.me.uk CC: lebedev...@gmail.com, llvm-bugs@lists.llvm.org, spatel+l...@rotateright.com As suggested on D61830: > Also, do we want to unfold and (shift x, c1), c2 / shift (and x, c1), c2 ? > Not sure, under !TLI.shouldFoldConstantShiftPairToMask() or a new > shouldFoldMaskToConstantShiftPair(). -- 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 41875] New: Incorrect code is generated for rotation of 32-bit value to 32-bits
https://bugs.llvm.org/show_bug.cgi?id=41875
Bug ID: 41875
Summary: Incorrect code is generated for rotation of 32-bit
value to 32-bits
Product: clang
Version: 8.0
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P
Component: -New Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: esol...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org,
neeil...@live.com, richard-l...@metafoo.co.uk
I'm using https://clang.godbolt.org/ with the following settings:
Compiler: x86-64 clang 8.0.0
Options: -Os
Test code:
```
#include
extern uint32_t v32;
void rotate_32 (void)
{
uint32_t x = v32;
int n = 32;
v32 = (x >> n) | (x << (32 - n)); /* rotate right to 32-bits */
}
```
Disassembly:
```
rotate_32: # @rotate_32
mov dword ptr [rip + v32], -1
ret
```
I expect that value in v32 does not change, but -1 is loaded instead.
Also can be observed with other clang version and other optimization levels
(-O1, -O2, -O3).
--
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 41875] Incorrect code is generated for rotation of 32-bit value to 32-bits
https://bugs.llvm.org/show_bug.cgi?id=41875 Sanjay Patel changed: What|Removed |Added Resolution|--- |INVALID CC||spatel+l...@rotateright.com Status|NEW |RESOLVED --- Comment #1 from Sanjay Patel --- The function invokes undefined behavior, so anything is possible. You can test for that by adding a 'main' wrapper and: $ clang -fsanitize=undefined 41875.c $ ./a.out 41875.c:9:14: runtime error: shift exponent 32 is too large for 32-bit type 'uint32_t' (aka 'unsigned int') For safe code and likely better code optimization, you may want to use the clang builtins for bitwise rotation: https://clang.llvm.org/docs/LanguageExtensions.html#builtin-functions -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 40758] [X86][SSE] Adjust shouldFoldConstantShiftPairToMask for targets with fast constant shifts
https://bugs.llvm.org/show_bug.cgi?id=40758 Simon Pilgrim changed: What|Removed |Added Fixed By Commit(s)|r359293 |r359293,r360684 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Simon Pilgrim --- rL360684 - scalar support -- 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 41876] New: std::hash should not accept std::basic_strings with custom character traits
https://bugs.llvm.org/show_bug.cgi?id=41876 Bug ID: 41876 Summary: std::hash should not accept std::basic_strings with custom character traits Product: libc++ Version: 8.0 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: unassignedclangb...@nondot.org Reporter: m...@groundctl.com CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com libc++ provides a specialization of std::hash that works for arbitrary instantiations of std::basic_string. This can produce incorrect behavior for basic_string instantiations with custom character traits that override equality (e.g. traits for case-insensitive comparison). Since the standard only requires that hash for for the typedefed instantiations (e.g. hash, hash, etc), libc++ should not support hashing basic_strings with custom character traits to avoid incorrect behavior. -- 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 41877] New: [coroutines] escaping alloca from inlined function should not be included in the coroutine frame
https://bugs.llvm.org/show_bug.cgi?id=41877
Bug ID: 41877
Summary: [coroutines] escaping alloca from inlined function
should not be included in the coroutine frame
Product: new-bugs
Version: trunk
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: new bugs
Assignee: unassignedb...@nondot.org
Reporter: gornisha...@gmail.com
CC: htmldevelo...@gmail.com, llvm-bugs@lists.llvm.org
https://godbolt.org/z/CCl-bg
CoroFrame analysis needs to pay attention to the lifetime.begin and .end
markers when deciding whether an escaping alloca should become part of the
coroutine frame or not.
In the example linked an pasted here for convenience:
// -std=c++2a -stdlib=libc++ -S -emit-llvm -g0 -O2
#include
using namespace std::experimental;
struct coro {
struct promise_type {
suspend_always initial_suspend() { return {};}
suspend_always final_suspend() { return {};}
void return_void() {}
void unhandled_exception() {}
coro get_return_object(){ return{}; }
};
};
struct A {
~A();
};
void async(void*) noexcept;
struct Awaiter{
bool await_ready() { return false; }
void await_resume() {}
void await_suspend(coroutine_handle<> h) {
A a;
async(h.address());
}
};
coro f() {
co_await Awaiter{};
}
await_suspend will get inlined into "f".
Address of a local variable "a" escapes (to a destructor call).
The correct lowering is that A should no be included into the coroutine frame,
since its lifetime ends after the call to "async".
However, currently CoroFrame does not pay attention to the lifetime markers and
will make A to be part of the coroutine frame that may get destroyed before
async returns leading to bad outcomes.
CoroFrame needs to be improved to take advantage of lifetime marker
information. If we go there, and completely understand the lifetime of very
variable, we could also pack variables tighter in the coroutine frame.
Looking at the IR emitted right now, we can observe the problem:
1) Struct A is included in the coroutine frame
%_Z1fv.Frame = type { void (%_Z1fv.Frame*)*, void (%_Z1fv.Frame*)*,
%"struct.coro::promise_type", i2, %struct.A }
2) A is touched after we called async (and coroutine frame could be destroyed
there)
define internal fastcc void @_Z1fv.resume(%_Z1fv.Frame*) #0 personality i8* ...
; preds = %1
%6 = bitcast %_Z1fv.Frame* %0 to i8*
store i2 1, i2* %2, align 1
%7 = getelementptr inbounds %_Z1fv.Frame, %_Z1fv.Frame* %0, i64 0, i32 4
%8 = getelementptr inbounds %struct.A, %struct.A* %7, i64 0, i32 0
tail call void @llvm.lifetime.start.p0i8(i64 1, i8* nonnull %8) #2
tail call void @_Z5asyncPv(i8* %6) #2
tail call void @_ZN1AD1Ev(%struct.A* nonnull %7) #2 ; < BOOM
tail call void @llvm.lifetime.end.p0i8(i64 1, i8* nonnull %8) #2
...
}
--
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@lists.llvm.org
https://bugs.llvm.org/show_bug.cgi?id=41853 Alina Sbirlea changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #3 from Alina Sbirlea --- Should be resolved by r360697. -- 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 41404] Provide coverage stack depth tracing instrumentation.
https://bugs.llvm.org/show_bug.cgi?id=41404 Mitch Phillips changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #1 from Mitch Phillips --- This ended up being an unrelated bug, wherein the Android build tree would generate unsanitized mutants of statically linked objects, which would then not pull in the fuzzer dependencies. Fixing the build system to ensure that the fuzzer-no-link wasn't lost fixed this issue. -- 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 41878] New: wasm-ld: --trace doesn't indicate where some symbols are referenced
https://bugs.llvm.org/show_bug.cgi?id=41878 Bug ID: 41878 Summary: wasm-ld: --trace doesn't indicate where some symbols are referenced Product: lld Version: unspecified Hardware: Other OS: other Status: NEW Severity: enhancement Priority: P Component: All Bugs Assignee: unassignedb...@nondot.org Reporter: dan433...@gmail.com CC: llvm-bugs@lists.llvm.org, peter.sm...@linaro.org, s...@chromium.org While debugging https://github.com/CraneStation/wasi-sdk/issues/30, I had a testcase that was linking in `__cxa_demangle`, and I wanted to know what was pulling it in. The `--trace` option told me this: /opt/wasi-sdk/share/sysroot/lib/wasm32-wasi/libc++abi.a: lazy definition of __cxa_demangle /opt/wasi-sdk/share/sysroot/lib/wasm32-wasi/libc++abi.a(cxa_demangle.cpp.o): definition of __cxa_demangle This doesn't actually indicate where the symbol is referenced from. The answer turned out to be that it was referenced from cxa_default_handlers.cpp.o in the same libc++abi.a file. I can provide my lib++abi.a if that helps. -- 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 17751] [intel inline asm] Crash when using 'short' keyword in intel assembly jumps instructions
https://bugs.llvm.org/show_bug.cgi?id=17751 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Reid Kleckner --- Looks like this was fixed in r284211. -- 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 36493] clang windows is emitting column information
https://bugs.llvm.org/show_bug.cgi?id=36493 Reid Kleckner changed: What|Removed |Added Fixed By Commit(s)||r279765 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #5 from Reid Kleckner --- Adrian fixed this in r279765. -- 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 27230] Naked functions that return values are broken
https://bugs.llvm.org/show_bug.cgi?id=27230 Reid Kleckner changed: What|Removed |Added CC||r...@google.com Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Reid Kleckner --- This looks like it was fixed, probably by r325788, which improved naked function handling across many IPO transforms. -- 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 36078] __attribute__((naked)) function loses parameter
https://bugs.llvm.org/show_bug.cgi?id=36078 Reid Kleckner changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Reid Kleckner --- This was fixed by r325788. -- 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 24556] naked functions with parameters are impossible to use correctly
https://bugs.llvm.org/show_bug.cgi?id=24556 Reid Kleckner changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #2 from Reid Kleckner --- I think this is working as intended for now. We reject these parameter usages up front: t.cpp:34:13: error: parameter references not allowed in naked functions , "l"(aSignal), "l"(aInfo), "l"(aContext) ^ t.cpp:19:16: note: attribute is here __attribute__((naked)) void ^ It's not as helpful as we could hypothetically be, but at least the user knows what to do: refer to the parameters manually by register or memory location. -- 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 41879] New: Please can we get a component for "wasm" under "lld"
https://bugs.llvm.org/show_bug.cgi?id=41879 Bug ID: 41879 Summary: Please can we get a component for "wasm" under "lld" Product: Bugzilla Admin Version: unspecified Hardware: PC OS: All Status: NEW Severity: enhancement Priority: P Component: Products Assignee: unassignedb...@nondot.org Reporter: s...@chromium.org CC: kristof.be...@gmail.com, llvm-bugs@lists.llvm.org, r...@google.com, t.p.northo...@gmail.com The other 3 lld ports have components but wasm doesn't yet. -- 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 41860] Merge r360512 into the 8.0 branch : [X86] Don't emit MOVNTDQA loads from fast-isel without SSE4.1.
https://bugs.llvm.org/show_bug.cgi?id=41860 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Status|NEW |RESOLVED Fixed By Commit(s)|r360512 |r360512 r360749 --- Comment #3 from Tom Stellard --- Merged: r360749 -- 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 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 41860, which changed state. Bug 41860 Summary: Merge r360512 into the 8.0 branch : [X86] Don't emit MOVNTDQA loads from fast-isel without SSE4.1. https://bugs.llvm.org/show_bug.cgi?id=41860 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41221] [meta] 8.0.1 Release Blockers
https://bugs.llvm.org/show_bug.cgi?id=41221 Bug 41221 depends on bug 41820, which changed state. Bug 41820 Summary: Merge r356982 into the 8.0 branch : [llvm-dlltool] Set a proper machine type for weak symbol object files https://bugs.llvm.org/show_bug.cgi?id=41820 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug.___ llvm-bugs mailing list llvm-bugs@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
[llvm-bugs] [Bug 41820] Merge r356982 into the 8.0 branch : [llvm-dlltool] Set a proper machine type for weak symbol object files
https://bugs.llvm.org/show_bug.cgi?id=41820 Tom Stellard changed: What|Removed |Added Resolution|--- |FIXED Fixed By Commit(s)|r356982 |r356982 r360750 Status|NEW |RESOLVED --- Comment #5 from Tom Stellard --- Merged: r360750 -- 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 41879] Please can we get a component for "wasm" under "lld"
https://bugs.llvm.org/show_bug.cgi?id=41879 Kristof Beyls changed: What|Removed |Added Resolution|--- |FIXED CC||kristof.be...@arm.com Status|NEW |RESOLVED --- Comment #1 from Kristof Beyls --- Hi Sam, I just created a wasm component under lld. I added yourself to the default cc list. If other people should be added too, let us know! Thanks, Kristof -- 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
