-
Notifications
You must be signed in to change notification settings - Fork 3
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
[AutoBump] Merge with 3c537459 (Aug 20) (6) #359
base: bump_to_2d50029f
Are you sure you want to change the base?
Commits on Aug 20, 2024
-
[MLIR] Introduce a SelectLikeOpInterface (llvm#104751)
This commit introduces a `SelectLikeOpInterface` that can be used to handle select-like operations generically. Select operations are similar to control flow operations, as they forward operands depending on conditions. This is the reason why it was placed to the already existing control flow interfaces.
Configuration menu - View commit details
-
Copy full SHA for bf68e90 - Browse repository at this point
Copy the full SHA bf68e90View commit details -
[Coroutines] [NFCI] Don't search the DILocalVariable for __promise wh…
…en constructing the debug varaible for __coro_frame As the title mentioned, do not search for the DILocalVariable for __promise when constructing the debug variable for __coro_frame. This should make sense because the debug variable of `__coro_frame` shouldn't dependent on the debug variable of `__promise`. And actually, it is not. Currently, we search the debug variable for `__promise` only because we want to get the debug location and the debug scope for the `__promise`. However, we can construct the debug location directly from the debug scope of the being compiled function. Then it is not necessary any more to search the `__promise` variable. And this patch makes the codes to construct the debug variable for `__coro_frame` to be more stable. Now we will always be able to construct the debug variable for the coroutine frame no matter if we found the debug variable for the __promise or not. This patch is not strictly NFC but it is intended to not affect any end users.
Configuration menu - View commit details
-
Copy full SHA for 08a0dec - Browse repository at this point
Copy the full SHA 08a0decView commit details -
[IR] Check that arguments of naked function are not used (llvm#104757)
Verify that the arguments of a naked function are not used. They can only be referenced via registers/stack in inline asm, not as IR values. Doing so will result in assertion failures in the backend. There's probably more that we should verify, though I'm not completely sure what the constraints are (would it be correct to require that naked functions are exactly an inline asm call + unreachable, or is more allowed?) Fixes llvm#104718.
Configuration menu - View commit details
-
Copy full SHA for 472c79c - Browse repository at this point
Copy the full SHA 472c79cView commit details -
[Coroutines] Fix -Wunused-variable in CoroFrame.cpp (NFC)
/llvm-project/llvm/lib/Transforms/Coroutines/CoroFrame.cpp:1124:15: error: unused variable 'PromiseAlloca' [-Werror,-Wunused-variable] AllocaInst *PromiseAlloca = Shape.getPromiseAlloca(); ^ 1 error generated.
Configuration menu - View commit details
-
Copy full SHA for d48b807 - Browse repository at this point
Copy the full SHA d48b807View commit details -
Configuration menu - View commit details
-
Copy full SHA for c29aba7 - Browse repository at this point
Copy the full SHA c29aba7View commit details -
[MLIR][Python] remove unused init python file (llvm#104890)
remove unused `__init__.py` under `mlir/python/mlir/extras`
Configuration menu - View commit details
-
Copy full SHA for f5f0055 - Browse repository at this point
Copy the full SHA f5f0055View commit details -
[LLD][COFF] Detect weak reference cycles. (llvm#104463)
Instead of entering an infinite loop.
Configuration menu - View commit details
-
Copy full SHA for 513e0af - Browse repository at this point
Copy the full SHA 513e0afView commit details -
[DataLayout] Refactor the rest of
parseSpecification
(llvm#104545)The aim is to improve test coverage of data layout string parsing. Pull Request: llvm#104545
Configuration menu - View commit details
-
Copy full SHA for c91cc45 - Browse repository at this point
Copy the full SHA c91cc45View commit details -
[LV] Simplify !UserVF.isZero() -> UserVF (NFC).
Address post-commit comment for b8dccb7 to simplify code.
Configuration menu - View commit details
-
Copy full SHA for 7452014 - Browse repository at this point
Copy the full SHA 7452014View commit details -
Configuration menu - View commit details
-
Copy full SHA for a6d81cd - Browse repository at this point
Copy the full SHA a6d81cdView commit details -
[lldb][AIX] 1. Avoid namespace collision on other platforms (llvm#104679
) This PR is in reference to porting LLDB on AIX. Link to discussions on llvm discourse and github: 1. https://discourse.llvm.org/t/port-lldb-to-ibm-aix/80640 2. llvm#101657 The complete changes for porting are present in this draft PR: llvm#102601 The changes on this PR are intended to avoid namespace collision for certain typedefs between lldb and other platforms: 1. tid_t --> lldb::tid_t 2. offset_t --> lldb::offset_t
Configuration menu - View commit details
-
Copy full SHA for b804516 - Browse repository at this point
Copy the full SHA b804516View commit details -
[Coroutines] Salvage the debug information for coroutine frames withi…
…n optimizations This patch tries to salvage the debug information for the coroutine frames within optimizations by creating the help alloca varaibles with optimizations too. We didn't do this when I implement it initially. I roughtly remember the reason was, we feel the additional help alloca variable may pessimize the performance, which is almost the most important thing under optimizations. But now, it looks like the new inserted help alloca variables can be optimized out by the following optimizations. So it looks like the time to make it available within optimizations. And also, it looks like the following optimizations will convert the generated dbg.declare instrinsic into dbg.value intrinsic within optimizations. In LLVM's test, there is a slightly regression that a dbg.declare for the promise object failed to be remained after this change. But it looks like we won't have a chance to see dbg.declare for the promise object when we split the coroutine as that dbg.declare will be converted into a dbg.value in early stage. So everything looks fine.
Configuration menu - View commit details
-
Copy full SHA for 522c253 - Browse repository at this point
Copy the full SHA 522c253View commit details -
[llvm][GitHub] Fix formatting of new contributor comments
GitHub won't reflow the text unless we put it all on one line. If we try to make our own paragrpahs it comes out too narrow or too wide.
Configuration menu - View commit details
-
Copy full SHA for 5adbce0 - Browse repository at this point
Copy the full SHA 5adbce0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 66953c9 - Browse repository at this point
Copy the full SHA 66953c9View commit details -
[clang][bytecode] Fix initializing base casts (llvm#104901)
Use delegate() there. To fix a follow-up problem, abort when a cast ends up on a valid Pointer that isn't a base class.
Configuration menu - View commit details
-
Copy full SHA for ba7dadf - Browse repository at this point
Copy the full SHA ba7dadfView commit details -
[Clang][test] Add bytecode interpreter tests for floating comparison …
…functions (llvm#104703) See also: llvm#94118, 7180170
Configuration menu - View commit details
-
Copy full SHA for f1b6427 - Browse repository at this point
Copy the full SHA f1b6427View commit details -
[mlir][EmitC] Do not convert illegal types in EmitC (llvm#104571)
This patch adds check for unsupported types in emitc, which fixes a crash. Fix llvm#103706.
Configuration menu - View commit details
-
Copy full SHA for 3c53745 - Browse repository at this point
Copy the full SHA 3c53745View commit details
Commits on Sep 20, 2024
-
Configuration menu - View commit details
-
Copy full SHA for f011f11 - Browse repository at this point
Copy the full SHA f011f11View commit details