Instrument the linking process as a detailed step in the compile stage

Open
#2,671 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
65/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
compilers, observability

Research direction

Start with the QJIT class and its existing instrumentation for the pre-compilation, capture, generate_ir, compile, and run stages. Trace the Python-side linking step and make sure the instrumentation report includes linking as an additional compile sub-stage.

Written by the indexing model from the issue text.

Description

enhancement frontend

Catalyst comes built-in with some instrumentation capabilities which are useful to get a quick overview over where time is spent in the compilation process. The instrumentation generally measures the main stages as defined in the QJIT class: pre-compilation, capture, generate_ir, compile, and run. However, it also supports reporting additional sub-stages such as the different pipelines run at the mlir level, as well as mlir-to-llvmir translation and object code generation. The linking step however, which is done from Python, is not explicitly measured.

Dominant language
Python
Stars
234
Forks
84
Avg merge
2d 15h
Merged PRs (30d)
66

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from PennyLaneAI/catalyst

All issues in PennyLaneAI/catalyst

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.