- Nov 01, 2020
-
-
Florian Hahn authored
This patch updates DSE + MemorySSA to use the same check as the legacy implementation to determine if a location is killed by a free call. This changes the existing behavior so that a free does not kill locations before the start of the freed pointer. This should fix PR48036.
-
Florian Hahn authored
The new test cases are inspired by PR48036.
-
Reid Kleckner authored
I don't see any warnings from lld.wasm locally. Needs more investigation.
-
Reid Kleckner authored
I had envisioned the ghash step as a big up front step, but as currently written, the timers are nested, and we are notionally adding types from objects, so we might as well arrange the timers this way.
-
Simon Pilgrim authored
-
Kostya Kortchinsky authored
This CL introduces the Fuchsia versions of the existing platform specific functions. For Fuchsia, we need to track the VMAR (https://fuchsia.dev/fuchsia-src/reference/kernel_objects/vm_address_region) of the Guarded Pool mapping, and for this purpose I added some platform specific data structure that remains empty on POSIX platforms. `getThreadID` is not super useful for Fuchsia so it's just left as a stub for now. While testing the changes in my Fuchsia tree, I realized that `guarded_pool_allocator_tls.h` should have closed the namespace before including `GWP_ASAN_PLATFORM_TLS_HEADER`, otherwise drama ensues. This was tested in g3, upstream LLVM, and Fuchsia (with local changes). Differential Revision: https://reviews.llvm.org/D90483
-
Florian Hahn authored
This reverts the revert commit a1b53db3. This patch includes a fix for a reported issue, caused by matchSelectPattern returning UMIN for selects of pointers in some cases by looking to some connected casts. For now, ensure integer instrinsics are only returned for selects of ints or int vectors.
-
Mark de Wever authored
Adds a diagnostic when the user annotates an `if constexpr` with a likelihood attribute. The `if constexpr` statement is evaluated at compile time so the attribute has no effect. Annotating the accompanied `else` with a likelihood attribute has the same effect as annotating a generic statement. Since the attribute there is most likely not intended, a diagnostic will be issued. Since the attributes can't conflict, the "conflict" won't be diagnosed for an `if constexpr`. Differential Revision: https://reviews.llvm.org/D90336
-
Mark de Wever authored
The attribute has no effect on a do statement since the path of execution will always include its substatement. It adds a diagnostic when the attribute is used on an infinite while loop since the codegen omits the branch here. Since the likelihood attributes have no effect on a do statement no diagnostic will be issued for do [[unlikely]] {...} while(0); Differential Revision: https://reviews.llvm.org/D89899
-
- Oct 31, 2020
-
-
Paul C. Anagnostopoulos authored
They occurred in one NVPTX file and some test files. Differential Revision: https://reviews.llvm.org/D90513
-
David Sanders authored
On Windows the --use-color option cannot be used for its originally intended purpose of forcing color when piping stdout, since Windows does not use ANSI escape codes by default. This change turns on ANSI escape codes on Windows when forcing color to a non-displayed stdout (e.g. piped).
-
David Green authored
If the elt size is unknown due to it being a pointer, a comparison against 0 will cause an assert. Make sure the elt size is large enough before comparing and for the moment just return the scalar cost.
-
Serge Pavlov authored
This test fails on buildbots where CPU architecture does not fully support constrained intrinsics.
-
Simon Pilgrim authored
This is the last of the rotate->funnel shift InstCombine generalizations for PR46896 We still have foldGuardedRotateToFunnelShift to deal with in AggressiveInstCombine Differential Revision: https://reviews.llvm.org/D90382
-
Simon Pilgrim authored
Fixes a number of cppcheck remarks.
-
Simon Pilgrim authored
Fixes a cppcheck remark.
-
Simon Pilgrim authored
Fixes a number of cppcheck remarks.
-
Simon Pilgrim authored
Fixes a number of cppcheck remarks.
-
Andrea Di Biagio authored
This is likely to be a regressigion introduced by my last refactoring of the LSUnit (commit 5578ec32). Before this patch, the "CurrentStoreBarrierGroupID" index was not correctly reset on store barrier executions. This was leading to unexpected crashes like the one reported as PR48024.
-
Simon Pilgrim authored
Silences cppcheck mismatch warnings.
-
Simon Pilgrim authored
-
Simon Pilgrim authored
Fixes cppcheck warning.
-
Simon Pilgrim authored
X86OutgoingValueHandler already has a MIB member
-
Simon Pilgrim authored
-
Simon Pilgrim authored
Silences cppcheck mismatch warnings.
-
Simon Pilgrim authored
Caught by cppcheck - appears to be a copy+paste typo as the other var is an iterator that does need the &* pointer operation.
-
Pedro Gonnet authored
Changed two references to developers as "he" or "him" to the more neutral "they". Reviewed By: JDevlieghere, sylvestre.ledru Differential Revision: https://reviews.llvm.org/D78807
-
Vitaly Buka authored
They block bot upgrade to NDK 21.
-
Serge Pavlov authored
Pragma 'clang fp' is extended to support a new option, 'exceptions'. It allows to specify floating point exception behavior more flexibly. Differential Revision: https://reviews.llvm.org/D89849
-
Nikita Popov authored
Previously, !noalias and !alias.scope metadata on the call site was applied as part of CloneAliasScopeMetadata(), which short-circuits if the callee does not use any noalias metadata itself. However, these two things have no relation to each other. Consistently apply !noalias and !alias.scope metadata by integrating this into an existing function that handled !llvm.access.group and !llvm.mem.parallel_loop_access metadata. The handling for all of these metadata kinds essentially the same.
-
Nikita Popov authored
Test the case where the callee does not use noalias metadata itself. This case is currently handled inconsistently.
-
Petr Hosek authored
While sanitizers don't use C++ standard library, we could still end up accidentally including or linking it just by the virtue of using the C++ compiler. Pass -nostdinc++ and -nostdlib++ to avoid these accidental dependencies. Reviewed By: smeenai, vitalybuka Differential Revision: https://reviews.llvm.org/D88922
-
Arthur Eubanks authored
This reverts commit 10f2a0d6. More uint64_t overflows.
-
Fangrui Song authored
Note, the deprecated AArch64 -msign-return-address= does not accept b-key. So delete the incorrect tests.
-
Fangrui Song authored
-
Jonas Devlieghere authored
Update XcodeSDKModuleTests for YAMLModuleTester changes in D90393.
-
LLVM GN Syncbot authored
-
Liu, Chen3 authored
This patch mainly made the following changes: 1. Support AVX-VNNI instructions; 2. Introduce ExplicitVEXPrefix flag so that vpdpbusd/vpdpbusds/vpdpbusds/vpdpbusds instructions only use vex-encoding when user explicity add {vex} prefix. Differential Revision: https://reviews.llvm.org/D89105 -
Petr Hosek authored
Part of D88922
-
Petr Hosek authored
And some other NFC parts of D88922
-