forked from llvm/llvm-project
-
Notifications
You must be signed in to change notification settings - Fork 3
Bump llvm next #46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Bump llvm next #46
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
Moved setting supported architecture to parent cmake configuration files so they can be read by both lib and test CMakeList.txt. Fixed issue with check-asan-abi that did not filter for current host architecture which caused x86_64 bots to run Arm64 tests. Added x86_64 as a supported arch to the test cmake file. rdar://110017569 Differential Revision: https://reviews.llvm.org/D151846
…dWrap from AVGFLOOR/CEIL transform. Use computeOverflowForUnsignedAdd and computeOverflowForSignedAdd instead. Unfortunately, this recomputes some known bits and sign bits we may have already computed, but was the easiest fix without a lot of restructuring. This recovers the regressions from D151472. Reviewed By: RKSimon Differential Revision: https://reviews.llvm.org/D151858
There were regressions in the testing framework due to none of the functioning buildbots having a 32 bit long. This allowed the 32 bit version of the strtointeger function to go untested. This patch adds tests for strtoint32 and strtoint64, which are internal testing functions that use constant integer sizes. It also fixes the tests to properly handle these situations. Reviewed By: sivachandra Differential Revision: https://reviews.llvm.org/D151935
Reviewed By: #libc, ldionne Spies: ldionne, libcxx-commits Differential Revision: https://reviews.llvm.org/D151573
…ectors The `vector.extract` folding patterns do not support 0-D vectors (actually, 0-D vector support couldn't even be implemented as a folding pattern as it would require replacing `vector.extract` with a `vector.extractelement` op). This patch is bailing out folding when 0-D vectors are found. Reviewed By: nicolasvasilache, hanchung Differential Revision: https://reviews.llvm.org/D151847
This PR adds support for shape casting from and to 0-D vectors. Reviewed By: nicolasvasilache, hanchung, awarzynski Differential Revision: https://reviews.llvm.org/D151851
… on sub-vectors Patterns that convert extract(transfer_read) into a scalar load where incorrectly triggering for cases where a sub-vector instead of a scalar was extracted. Reviewed By: nicolasvasilache, hanchung, awarzynski Differential Revision: https://reviews.llvm.org/D151862
This reverts commit 76d71f3.
…s earlier in the class hierarchy. Remove RISCVMaskedPseudo from vslideup/down. I hadn't intended to include them. I missed that they used the same classes as FMA. They weren't tested and I don't have a use case yet. This is also needed as I attempt refactor the classes to improve D151850.
This barely matters since 99% are converted to the generic intrinsic now, and the only real difference is the target intrinsic supports a variable test mask. Start propagating poison. Prefer folding to a defined result (false) for an undef test mask. Propagate undef for the first operand.
… paths With /winsysroot and without /machine, we don't know which paths to add to the search paths. We do autodetect machine type and add winsysroot search paths in SymbolTable::addFile(), but that happens after all input files are opened. So in the loop where we read files, if we fail to open a file we can retry with the winsysroot search path potentially added by reading a previous file. This will fail if we try to open something in the winsysroot before reading a file that can give us the architecture, but shrug. Fixes llvm#54409 Reviewed By: rnk Differential Revision: https://reviews.llvm.org/D151815
This patch implements minimal support for lowering function calls to callees with arguments and/or return values according to the RISC-V calling convention. Integer, pointer and aggregate types are supported. Feedback is very much appreciated. Reviewed By: arsenm Differential Revision: https://reviews.llvm.org/D75023
/data/llvm-project/llvm/lib/Target/RISCV/GISel/RISCVCallLowering.cpp:272:12: error: variable 'Index' set but not used [-Werror,-Wunused-but-set-variable] unsigned Index = 0; ^ 1 error generated.
There were two bugs here. eMatchTypeStartsWith searched for "symbol_name" by adding ".*" to the end of the symbol name and treating that as a regex, which isn't actually a regex for "starts with". The ".*" is in fact a no-op. When we finally get to comparing the name, we compare against whatever form of the name was in the accelerator table. But for C++ that might be the mangled name. We should also try demangled names here, since most users are going the see demangled not mangled names. I fixed these two bugs and added a bunch of tests for FindGlobalVariables. This change is in the DWARF parser code, so there may be a similar bug in PDB, but the test for this was already skipped for Windows, so I don't know about this. You might theoretically need to do this Mangled comparison in DWARFMappedHash::MemoryTable::FindByName except when we have names we always chop them before looking them up so I couldn't see any code paths that fail without that change. So I didn't add that to this patch. Differential Revision: https://reviews.llvm.org/D151940
Formerly, we accepted and/prod reductions as a standard reduction but these change the semantics after sparsification by not looking at implicit zeros. Therefore, we only accept standard reductions that are insensitive to implicit vs. explicit zeros, and leave the more complex reductions to the sparse_tensor.reduce custom reduction implementation. Reviewed By: Peiming Differential Revision: https://reviews.llvm.org/D151929
This patch should address the crashes when parsing a the crash report frame dictionary. If the crash report is not symbolicated, the `symbolLocation` key will be missing. In that case, we should just use the `imageOffset`. rdar://109836386 Differential Revision: https://reviews.llvm.org/D151844 Signed-off-by: Med Ismail Bennani <[email protected]>
This patch changes the way we load a crash report into a scripted process by creating a empty target. To do so, it parses the architecture information from the report (for both the legacy and json format) and uses that to create a target that doesn't have any executable, like what we do when attaching to a process. For the legacy format, we mostly rely on the `Code Type` line, since the architure is an optional field on the `Binary Images` sections. However for the json format, we first try to get the architecture while parsing the image dictionary if we couldn't find it, we try to infer it using the "flavor" key when parsing the frame's registers. If the architecture is still not set after parsing the report, we raise an exception. rdar://107850263 Differential Revision: https://reviews.llvm.org/D151849 Differential Signed-off-by: Med Ismail Bennani <[email protected]>
Signed-off-by: Med Ismail Bennani <[email protected]>
Signed-off-by: Med Ismail Bennani <[email protected]>
I fixed some long-standing failures in SBTarget::FindGlobalVariables but the fix is in the the accelerator table lookups. I fixed it in the DWARF mappable tables but not everyone uses those, so I had to restrict the test to systems I know did.
BOLT may add an extra MCOperand as annotation, making the number of operands in MCInst different from MCInstrDesc information. A recent change broke our use as the last operand is no longer a cond code. Partially revert 287dd01 to rely on MCInstrDesc to access CondCode operand. Reviewed By: skan Differential Revision: https://reviews.llvm.org/D151930
…sttail call`, avoid sinking token type FuzzMutate didn't consider some corner cases and leads to mutation failure when mutating some modules. This patch fixes 3 bugs: - Add null check when encountering basic blocks without predecessor to avoid segmentation fault - Avoid insertion after `musttail call` instruction - Avoid sinking token type Unit tests are also added. Reviewed By: Peter Differential Revision: https://reviews.llvm.org/D151936
Otherwise, the various lists of headers have different content based on whether they are run on Windows or other platforms, which makes it really difficult to write .gen.py tests correctly. Differential Revision: https://reviews.llvm.org/D151913
This allows removing a bunch of boilerplate from the test suite and reducing the amount of manual stuff contributors have to do when they add a new public header. Differential Revision: https://reviews.llvm.org/D151830
As with D151615, which changed `GetIndexOfChildMemberWithName` to take a `StringRef` instead of a `ConstString`, this change does the same for `GetIndexOfChildWithName`. Differential Revision: https://reviews.llvm.org/D151811
Following D151810, this changes `GetChildAtNamePath` to take a path of `StringRef` values instead of `ConstString`. Differential Revision: https://reviews.llvm.org/D151813
This was missed when the other dialects adopted it. Reviewed By: rriddle Differential Revision: https://reviews.llvm.org/D151410
To go with D149267 and D149967, this adds predicated mla/mls patterns, selected from select(mask, add(a, mul(b, c)), a) -> mla(a, mask, b, c). The existing patterns are eventually removed by D149967. Differential Revision: https://reviews.llvm.org/D149969
* TOSA: Extend verifier to reshape of to check newShape attr * TOSA: add initial verifier for SliceOp
…fe4a Matthias.update llvm to green 6cf7fe4
TOSA: Allow to transpose 7D tensors and higher
….bump_llvm_next green commit of Week of 05/29/2023
bb7d00f
to
59268a7
Compare
Bump to llvm green 2b4807 for torch-mlir
flemairen6
approved these changes
Jun 19, 2023
…t of week 06/05/2023)
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.
No description provided.