forked from llvm/llvm-project
-
Notifications
You must be signed in to change notification settings - Fork 5
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
[pull] main from llvm:main #752
Merged
Merged
Conversation
This file contains 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
All relevant operations have been switched to primarily use the strided layout, but still support the affine map layout. Update the relevant tests to use the strided format instead for compatibility with how ops now print by default. Reviewed By: nicolasvasilache Differential Revision: https://reviews.llvm.org/D134045
One of the vector transformation patterns has been indiscriminately converting layouts to affine maps. Leverage the strided form when possible. Reviewed By: nicolasvasilache, dcaballe Differential Revision: https://reviews.llvm.org/D134047
…; NFC Baseline tests for D131786
Wrap implicit dependencies in Label() so that they refer to @llvm-project, see https://bazel.build/rules/lib/Label#Label. This change allows lit_test() to be used from other bazel repositories.
We would diagnose use of `long long` as an extension in C89 and C++98 modes when the user spelled the type `long long` or used the `LL` literal suffix, but failed to diagnose when the literal had no suffix but required a `long long` to represent the value.
The test is failing because it lacks a target triple, so the number of diagnostics differs between Windows and Linux targets. This should correct the issue found by: https://lab.llvm.org/buildbot/#/builders/109/builds/46804
Uses double backticks where appropriate, changes some instances of GH12345 to be Issue 12345, etc.
…rn types can be mangled Reviewed By: ldionne, #libc Spies: libcxx-commits, jeroen.dobbelaere Differential Revision: https://reviews.llvm.org/D133196
It may help users to better understand the change by showing them a contrived code example which demonstrates the difference in behavior.
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.
See Commits and Changes for more details.
Created by pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )