Skip to content

Conversation

@dchigarev
Copy link
Contributor

mlir::ExecutionEngine(enableObjectDump=true) doesn't actually dump any module, but provides an ability to call ExecutionEngine::dumpToObjectFile(...) later (which only can dump to a file, while we want it to be dumped to std::err in OV integration).

Comment on lines +811 to +814
if (enableObjectDump) {
mod.dump();
}

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@AndreyPavlenko what do you think, should it be a separate option in OclModuleBuilderOptions? Or maybe we can add a bool parameter to OclModuleBuilder::build(..., bool dump_lowered_module=false)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should be a separate option, because enableObjectDump is used to dump the compiled object.
It could also be implemented without adding a new option, like here -

builderOpts.pipeline = opts.printIr ? [](OpPassManager &pm) {

@dchigarev
Copy link
Contributor Author

decided to implement this in #362

@dchigarev dchigarev closed this Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants