Found an issue with IC. Filled with minimal repro:...
# compiler
p
z
your descriptions are pretty terse and don't explain how the plugin example is supposed to work, but at a glance I don't see any usage of
LookupTracker
to report information to IC in your plugin
p
Hello, @Zac Sweers! Thanks for reply! Could you provide some link to example how to use LookupTracker in IR backend compiler plugin?
z
it's fairly self-explanatory if you look for usages in the compiler, and there were some added APIs around it in 2.2.20 to make things easier too
basically "this declaration is dirtied by this one"
p
Using LookupTracker (call record for dependent class) solves the problem. But anyway I wonder why not to automatically track for external usages in the compiler IR backend based on the resulting IR tree?