[MLIR] Add bufferization state class to OneShotBufferization pass by mscuttari · Pull Request #138143 · llvm/llvm-project (original) (raw)

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

[ Show hidden characters]({{ revealButtonHref }})

mscuttari

@mscuttari

@mscuttari mscuttari marked this pull request as ready for review

May 18, 2025 16:55

matthias-springer

@mscuttari

mscuttari added a commit that referenced this pull request

May 22, 2025

@mscuttari

…pass" (#141012)

Reverts #138143

The PR for the BufferizationState is temporarily reverted due to API incompatibilities that have been initially missed during the update and were not catched by PR checks.

llvm-sync bot pushed a commit to arm/arm-toolchain that referenced this pull request

May 22, 2025

@mscuttari @github-actions

…ferization pass" (#141012)

Reverts llvm/llvm-project#138143

The PR for the BufferizationState is temporarily reverted due to API incompatibilities that have been initially missed during the update and were not catched by PR checks.

mscuttari added a commit that referenced this pull request

May 23, 2025

@mscuttari

…41019)

Follow-up on #138143, which was reverted due to a missing update a method signature (more specifically, the bufferization interface for tensor::ConcatOp) that was not catched before merging. The old PR description is reported in the next lines.

This PR is a follow-up on #138125, and adds a bufferization state class providing information about the IR. The information currently consists of a cached list of symbol tables, which aims to solve the quadratic scaling of the bufferization task with respect to the number of symbols. The PR breaks API compatibility: the bufferize method of the BufferizableOpInterface has been enriched with a reference to a BufferizationState object.

The bufferization state must be kept in a valid state by the interface implementations. For example, if an operation with the Symbol trait is inserted or replaced, its parent SymbolTable must be updated accordingly (see, for example, the bufferization of arith::ConstantOp, where the symbol table of the module gets the new global symbol inserted). Similarly, the invalidation of a symbol table must be performed if an operation with the SymbolTable trait is removed (this can be performed using the invalidateSymbolTable method, introduced in #138014).

sivan-shani pushed a commit to sivan-shani/llvm-project that referenced this pull request

Jun 3, 2025

@mscuttari @sivan-shani

…vm#138143)

This PR is a follow-up on llvm#138125, and adds a bufferization state class providing information about the IR. The information currently consists of a cached list of symbol tables, which aims to solve the quadratic scaling of the bufferization task with respect to the number of symbols. The PR breaks API compatibility: the bufferize method of the BufferizableOpInterface has been enriched with a reference to a BufferizationState object.

The bufferization state must be kept in a valid state by the interface implementations. For example, if an operation with the Symbol trait is inserted or replaced, its parent SymbolTable must be updated accordingly (see, for example, the bufferization of arith::ConstantOp, where the symbol table of the module gets the new global symbol inserted). Similarly, the invalidation of a symbol table must be performed if an operation with the SymbolTable trait is removed (this can be performed using the invalidateSymbolTable method, introduced in llvm#138014).

sivan-shani pushed a commit to sivan-shani/llvm-project that referenced this pull request

Jun 3, 2025

@mscuttari @sivan-shani

…pass" (llvm#141012)

Reverts llvm#138143

The PR for the BufferizationState is temporarily reverted due to API incompatibilities that have been initially missed during the update and were not catched by PR checks.

sivan-shani pushed a commit to sivan-shani/llvm-project that referenced this pull request

Jun 3, 2025

@mscuttari @sivan-shani

…vm#141019)

Follow-up on llvm#138143, which was reverted due to a missing update a method signature (more specifically, the bufferization interface for tensor::ConcatOp) that was not catched before merging. The old PR description is reported in the next lines.

This PR is a follow-up on llvm#138125, and adds a bufferization state class providing information about the IR. The information currently consists of a cached list of symbol tables, which aims to solve the quadratic scaling of the bufferization task with respect to the number of symbols. The PR breaks API compatibility: the bufferize method of the BufferizableOpInterface has been enriched with a reference to a BufferizationState object.

The bufferization state must be kept in a valid state by the interface implementations. For example, if an operation with the Symbol trait is inserted or replaced, its parent SymbolTable must be updated accordingly (see, for example, the bufferization of arith::ConstantOp, where the symbol table of the module gets the new global symbol inserted). Similarly, the invalidation of a symbol table must be performed if an operation with the SymbolTable trait is removed (this can be performed using the invalidateSymbolTable method, introduced in llvm#138014).

ajaden-codes pushed a commit to Jaddyen/llvm-project that referenced this pull request

Jun 6, 2025

@mscuttari @Jaddyen

…vm#138143)

This PR is a follow-up on llvm#138125, and adds a bufferization state class providing information about the IR. The information currently consists of a cached list of symbol tables, which aims to solve the quadratic scaling of the bufferization task with respect to the number of symbols. The PR breaks API compatibility: the bufferize method of the BufferizableOpInterface has been enriched with a reference to a BufferizationState object.

The bufferization state must be kept in a valid state by the interface implementations. For example, if an operation with the Symbol trait is inserted or replaced, its parent SymbolTable must be updated accordingly (see, for example, the bufferization of arith::ConstantOp, where the symbol table of the module gets the new global symbol inserted). Similarly, the invalidation of a symbol table must be performed if an operation with the SymbolTable trait is removed (this can be performed using the invalidateSymbolTable method, introduced in llvm#138014).

ajaden-codes pushed a commit to Jaddyen/llvm-project that referenced this pull request

Jun 6, 2025

@mscuttari @Jaddyen

…pass" (llvm#141012)

Reverts llvm#138143

The PR for the BufferizationState is temporarily reverted due to API incompatibilities that have been initially missed during the update and were not catched by PR checks.