[all-commits] [llvm/llvm-project] cb3016: [flang] Use LLVM dialect ops for stack save/restor...
jeanPerier via All-commits
all-commits at lists.llvm.org
Tue Sep 10 05:33:35 PDT 2024
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: cb30169422446b79d99df12b4cf5ab3d9d46d54c
https://github.com/llvm/llvm-project/commit/cb30169422446b79d99df12b4cf5ab3d9d46d54c
Author: jeanPerier <jperier at nvidia.com>
Date: 2024-09-10 (Tue, 10 Sep 2024)
Changed paths:
M flang/include/flang/Optimizer/CodeGen/CGPasses.td
M flang/lib/Optimizer/CodeGen/TargetRewrite.cpp
M flang/test/Fir/struct-passing-x86-64-one-field-inreg.fir
M flang/test/Fir/struct-passing-x86-64-several-fields-inreg.fir
M flang/test/Fir/target-rewrite-complex16.fir
Log Message:
-----------
[flang] Use LLVM dialect ops for stack save/restore in target-rewrite (#107879)
Mostly NFC, I was bothered by the declaration that were always made even
if unsued, and I think using LLVM Ops is nicer anyway with regards to
side effects here.
```
func.func private @llvm.stacksave.p0() -> !fir.ref<i8>
func.func private @llvm.stackrestore.p0(!fir.ref<i8>)
```
There are other places in lowering that are using the calls instead of
the LLVM intrinsics, but I will deal with them another time (the issue
there is mostly to get the proper address space for the llvm.ptr type).
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list