Details
-
User Story
-
Resolution: Done
-
P2: Important
-
None
-
None
-
8827af0fe (dev), f2889262c (dev), d18f6d694 (dev), 65d8be4b9 (6.8), 318ac4406 (dev), 4dab304ae (dev), 6a3e77125 (dev), 09f51978f (dev), 45c9d773e (6.8), cb52469a0 (6.8), 012f827c2 (6.8), c5676c854 (6.8), 7d36867bf (dev), 27cd91473 (6.9), 7b119f78e (6.8)
Description
Users generally would like to know whether the script compiler makes their code faster, and whether it's worth the longer compile times. That can't be answered without actual benchmarking. We can however provide some insights into what the Script Compiler is actually doing:
- Which/How many bindings and functions can actually get compiled?
- How much time was spent in the Script Compiler? Harder: How much in the compilation of the generated C++ code?
- Some statistics on reasons why we rejected bindings/functions – this might also help drive further development of the Script Compiler.
Given that the ScriptCompiler works per TU, we probably need an aggregation step as post-processing.
Lastly, and at a later point, the result could be used by the LSP to highlight compiled and non-compiled bindings differently.
Attachments
Issue Links
- split to
-
QTBUG-125995 Fix aotstats cmake support on Xcode
- Closed
-
QTBUG-126334 Visualize information collected by Script Compiler
- Reported
- mentioned in
-
Page Loading...