Max.fxml 1406.bump llvm to green commit #12
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
(a) Treat name as unsigned chars. (b) Refactor for better optimization of main loop. Differential Revision: https://reviews.llvm.org/D147890
99e52b6 re-generated that file with a clang-format version that differs from the CI's clang-format, leading to CI breakage.
- Update the `actions/download-artifact` action to version 3. - Use the major version of an action instead of specifying the minor or patch versions. Differential Revision: https://reviews.llvm.org/D148327
Avoids some regressions when the implementation of isKnownNeverNaN is replaced with computeKnownFPClass.
Limit turns out to be implemented in the exact same way for all calls to tryToVectorizeSequence(). So this patch removes it and implements it internally as a lambda function. Differential Revision: https://reviews.llvm.org/D148382
…o compare unnamed bit-fields If we look at class.bit p2 it tells us that that unnamed bit-fields are not members and class.compare.default p5 tells us that we should only compare non-static data members of the class. This fixes: llvm#61335 and llvm#61417 Differential Revision: https://reviews.llvm.org/D146329
…for Fuchsia"" This reverts commit 39ece75. Reverting because I suspect this is leading to the failures we see in fxbug.dev/125426. We're seeing unexpected OOMs and I suspect it's because this change makes c-style allocation functions use hwasan's allocator which might be worse than the default one (scudo). Reverting for now to see if this unblocks the clang roll.
Towards converting our use of llvm::StringView to std::string_view, remove a method that std::string_view doesn't have. This could be moved to the nascent llvm/ADT/StringViewExtras.h, but the use is highly localized to one TU. Move this to be a static function there. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D148375
added getchar and getchar_unlocked which are just wrappers getc and getc_unlocked respectively. Reviewed By: sivachandra, lntue, michaelrj Differential Revision: https://reviews.llvm.org/D147919
This refactoring was waiting on converting LLVM to C++17. Leave StringView.h and cleanup around for subsequent cleanup. Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D148384
…urrent target Catch accidentally used flags and match MCSectionELF.cpp `MCSectionELF::printSwitchToSection`. Reviewed By: aeubanks Differential Revision: https://reviews.llvm.org/D148386
The explicit `ignoring all compiler directives` reminder warning is no longer accurate. Any similar, more accurate message is best generated by the front end (change pending).
PATCHABLE_* instructions expand to up to 36-byte sleds. Updating the size of PATCHABLE instructions causes them to be outlined, so we need to add a check to prevent the outliner from considering basic blocks that contain PATCHABLE instructions. Differential Revision: https://reviews.llvm.org/D147982
Differential Revision: https://reviews.llvm.org/D147896
…`shl` can be zero.
Previously only return `shl` non-zero if the shift value was `1`. We
can expand this if we have some bounds on the shift count.
For example:
```
%cnt = and %c, 16 ; Max cnt == 16
%val = or %v, 4 ; val[2] is known one
%shl = shl %val, %cnt ; (val.known.one << cnt.maxval) != 0
```
Differential Revision: https://reviews.llvm.org/D147897
Alive2 Link: https://alive2.llvm.org/ce/z/mxZLJn Reviewed By: nikic Differential Revision: https://reviews.llvm.org/D147898
Fixes diagnostics reported against https://reviews.llvm.org/D148384 https://lab.llvm.org/buildbot/#/builders/127/builds/46749/steps/4/logs/stdio Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D148392
Future patch will set the current context as well. Existing callsite requires additional lock to find context. Differential Revision: https://reviews.llvm.org/D148390
After enabling ArgPromotion at lower opt levels, the body of this test was optimized away, and the CHECK lines no longer functioned. Setting -O0 is a hammer, but gets the test passing again, until code owners can find a better solution. Reviewed By: fmayer Differential Revision: https://reviews.llvm.org/D148396
Reviewed By: MaskRay Differential Revision: https://reviews.llvm.org/D148358
PrintIRInstrumentation::shouldPrintAfterPass accepts a pass ID instead of a pass name Reviewed By: aeubanks Differential Revision: https://reviews.llvm.org/D147394
We need to create a new type with transposed shape after transposing the operand in `CanonicalizeContractMatmulToMMT`. Reviewed By: kuhar, dcaballe Differential Revision: https://reviews.llvm.org/D148470
This reverts commit 82c02b7. Apparently, the original patch was not rebased onto `main
…` and `[` as `is` is a keyword in C# ensure there is always a space before the `[` regardless of `SpaceBeforeSquareBrackets` setting Fixes: llvm#61965 llvm#61965 Reviewed By: owenpan, HazardyKnusperkeks Differential Revision: https://reviews.llvm.org/D148472
…sting functions. This patch replaces the uses of PointerUnion.is function by llvm::isa, PointerUnion.get function by llvm::cast, and PointerUnion.dyn_cast by llvm::dyn_cast_if_present. This is according to the FIXME in the definition of the class PointerUnion. This patch does not remove them as they are being used in other subprojects. Reviewed By: mehdi_amini Differential Revision: https://reviews.llvm.org/D148449
This allows the subsequent code to access the E_IDENT fields, which will be used in the upcoming JITLink ppc64 backend (https://reviews.llvm.org/D148192).
- Separate the two test and only have TestSymbolFileJSON rely on strip. - Use different file names to make sure LLDB reloads the module. This should address all the post commit review from D148062.
Reviewed By: kwk Differential Revision: https://reviews.llvm.org/D143535
This patch updates the list of supported libs according to the latest changes to x86_64 Reviewed By: sivachandra Differential Revision: https://reviews.llvm.org/D147961
…n VPlan." This reverts commit 7fc0b30. Causes a clang hang when building xz utils, github issue llvm#62187.
The `__builtin_bswap{32,64}()` builtins (introduced in commit e07a421)
are missing from MSVC, which causes build errors when compiling LLDB on
Windows (tested with MSVC 19.34.31943.0). This patch replaces the
builtins with either MSVC's `_byteswap_u{long,64}()` or the original
builtins, or the `bswap_{32,64}()` functions from byteswap.h, depending
on which ones are available.
Reviewed By: bulbazord
Differential Revision: https://reviews.llvm.org/D148541
Use the assembly format with custom parser/printer for specific clauses instead of a full custom parser/printer. Reviewed By: PeteSteinfeld Differential Revision: https://reviews.llvm.org/D148391
Partial revert of commit ee91799. I can't reproduce the error locally, so let's revert it to keep the bots happy.
Ferdinand.llvm bump may 0305
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT FILE A PULL REQUEST
This repository does not accept pull requests. Please follow http://llvm.org/docs/Contributing.html#how-to-submit-a-patch for contribution to LLVM.
DO NOT FILE A PULL REQUEST