[all-commits] [llvm/llvm-project] 996639: [MLIR][BufferResultsToOutParamsPass] Add Option to...
Veera via All-commits
all-commits at lists.llvm.org
Sun Nov 9 21:08:43 PST 2025
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 996639d6ebb86ff15a8c99b67f1c2e2117636ae7
https://github.com/llvm/llvm-project/commit/996639d6ebb86ff15a8c99b67f1c2e2117636ae7
Author: Veera <32646674+veera-sivarajan at users.noreply.github.com>
Date: 2025-11-09 (Sun, 09 Nov 2025)
Changed paths:
M mlir/include/mlir/Dialect/Bufferization/Transforms/Passes.h
M mlir/include/mlir/Dialect/Bufferization/Transforms/Passes.td
M mlir/lib/Dialect/Bufferization/Transforms/BufferResultsToOutParams.cpp
A mlir/test/Transforms/buffer-results-to-out-params-modify-public-functions.mlir
Log Message:
-----------
[MLIR][BufferResultsToOutParamsPass] Add Option to Modify Public Function's Signature (#167248)
Since https://github.com/llvm/llvm-project/pull/162441,
`buffer-results-to-out-params` transforms `private` functions only.
But, as mentioned in
https://github.com/llvm/llvm-project/pull/162441#issuecomment-3404195242,
this is a breaking change for pipelines handling C code. Our pipeline
@EfficientComputer is also affected by this breaking change.
Therefore, this PR adds an opt-in flag to allow `public` functions to be
transformed by `BufferResultsToOutParamsPass`.
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