aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
diff options
context:
space:
mode:
authorMaksim Levental <maksim.levental@gmail.com>2025-10-27 12:22:13 -0700
committerGitHub <noreply@github.com>2025-10-27 12:22:13 -0700
commitcd9d48777e3b1f2d46791e7d834a80f1b6a14c74 (patch)
tree9391a7ff6a654de5927076955b8169b28f436ecd /lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp
parent267b5b8901fad878add53159e7a11050bec2e0f3 (diff)
downloadllvm-cd9d48777e3b1f2d46791e7d834a80f1b6a14c74.zip
llvm-cd9d48777e3b1f2d46791e7d834a80f1b6a14c74.tar.gz
llvm-cd9d48777e3b1f2d46791e7d834a80f1b6a14c74.tar.bz2
[MLIR][ExecutionEngine] don't dump decls (#164478)
Currently ExecutionEngine tries to dump all functions declared in the module, even those which are "external" (i.e., linked/loaded at runtime). E.g. ```mlir func.func private @printF32(f32) func.func @supported_arg_types(%arg0: i32, %arg1: f32) { call @printF32(%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 `printF32` can be provided at final build time (i.e., when the object file is linked to some executable or shlib). E.g, if our own `libmlir_c_runner_utils` is linked. So just skip functions which have no bodies during dump (i.e., are decls without defns).
Diffstat (limited to 'lldb/source/Plugins/Process/gdb-remote/ProcessGDBRemote.cpp')
0 files changed, 0 insertions, 0 deletions