diff options
author | Philip Lassen <plassen@groq.com> | 2025-08-04 23:36:02 -0700 |
---|---|---|
committer | GitHub <noreply@github.com> | 2025-08-05 08:36:02 +0200 |
commit | 95d9e8af64bc8e3f257553e2da01388bb72823fe (patch) | |
tree | 076c925d1cab4f01df351f86aec7d1c3044e253d /mlir/unittests/Bytecode/BytecodeTest.cpp | |
parent | 1eaf736384e6d1de1f9c23c8f60d872499b7cc97 (diff) | |
download | llvm-95d9e8af64bc8e3f257553e2da01388bb72823fe.zip llvm-95d9e8af64bc8e3f257553e2da01388bb72823fe.tar.gz llvm-95d9e8af64bc8e3f257553e2da01388bb72823fe.tar.bz2 |
[NFC][mlir] Update DataFlowFramework.h to be compatible with clang c++23 (#152040)
This change makes `DataFlowFramework.h` compatible with `clang++` and
`--std=c++23`.
Previously clang was checking the templated `DataFlowSolver::eraseState`
body before being instantiated. This resulted in issues with incomplete
types, and happened at least with `clang++-19`.
This is fixed by moving the definition of `DataFlowSolver::eraseState`
after the `AnalysisState`'s full class declaration.
For full context:
-
https://discourse.llvm.org/t/what-is-the-status-of-c-23-support-in-mlir/87674/12
Diffstat (limited to 'mlir/unittests/Bytecode/BytecodeTest.cpp')
0 files changed, 0 insertions, 0 deletions