[all-commits] [llvm/llvm-project] 73f651: [MLIR][ExecutionEngine] don't dump decls

[Maksim Levental via All-commits]

  Branch: refs/heads/users/makslevental/fix-ee
  Home:   https://github.com/llvm/llvm-project
  Commit: 73f651fa5473271738bbecec36b6c5c795173eb3
      https://github.com/llvm/llvm-project/commit/73f651fa5473271738bbecec36b6c5c795173eb3
  Author: Maksim Levental <maksim.levental at gmail.com>
  Date:   2025-10-21 (Tue, 21 Oct 2025)

  Changed paths:
    M mlir/lib/ExecutionEngine/ExecutionEngine.cpp

  Log Message:
  -----------
  [MLIR][ExecutionEngine] don't dump decls

Currently ExecutionEngine tries to dump all functions declared in the module, even thoughs which "external" (i.e., linked at runtime). E.g.

```mlir
module {
  func.func @supported_arg_types(%arg0: i32, %arg1: f32) {
    vector.print %arg0 : i32
    vector.print %arg1 : f32
    return
  }
}
```
fails with
```
Could not compile printF32:
  Symbols not found: [ __mlir_printF32 ]
Program aborted due to an unhandled Error:
Symbols not found: [ __mlir_printF32 ]
```
even though `mlir_printF32` can and is provided by our own `libmlir_c_runner_utils`, which is usually loaded by the engine but of course can also be linked/loaded at runtime by whatever thing links the object file produced from the above.

So just skip functions which have no bodies during dump (i.e., are decls without defns).



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications