Hi, debugging a compiler extension plugin (IR) wit...
# compiler
j
Hi, debugging a compiler extension plugin (IR) with AnalysisHandlerExtension and IrGeneratorExtension I see that IR Generation comes last. Is there any extension point, that runs after generation, so one could analyse all effective sources ? (so that any generated/transformed sources are again available for introspection/analysis)
s
Analysis happens on the frontend of the compiler, IR generation on the backend, so it is impossible to analyze IR generated code. You might want to use KSP for codegen with multiple passes