Questions about infersharp implementation

Hello!

Thanks for this tool and the PR about language-agnostic layer.

This issue is not going to report some bugs and features. I just wanna get answers to my a few questions, which are mainly about infersharp implementation.

• Why MethodBody can be found everywhere in cfg.json? And what’s the logic of it? Perhaps I fail to figure out what MethodBody means? (e.g Why LdargParser generates MethodBody node, while LdcParser doesn’t.)
• Is Metadata instruction useful? I wanna know the reason infersharp doesn’t implement it.
• The point I mostly concerned is whether infer can run some language-unrelated checkers with data (cfg.json & tenv.json) received from language-agnostic layer interface.

Many thanks!

[matjin]

In general, when the CIL corresponds to an SIL instruction, we create the corresponding SIL instruction which in turn gets added to a MethodBody node. Not all CIL have such a correspondence – for example, ldc refers to the pushing of a constant onto the CIL program stack but has no direct corresponding operation in SIL because the constant doesn’t come from a register. By contrast, ldarg refers to the pushing of an argument’s value onto the CIL program stack; this corresponds to the load of the argument register. Similarly, Initobj/Newarr refer to the creation of objects, which correspond to Call instructions in the SIL, hence we create MethodBody nodes to store these instructions.

[skyleaworlder]

In general, when the CIL corresponds to an SIL instruction, we create the corresponding SIL instruction which in turn gets added to a MethodBody node. Not all CIL have such a correspondence – for example, ldc refers to the pushing of a constant onto the CIL program stack but has no direct corresponding operation in SIL because the constant doesn’t come from a register. By contrast, ldarg refers to the pushing of an argument’s value onto the CIL program stack; this corresponds to the load of the argument register. Similarly, Initobj/Newarr refer to the creation of objects, which correspond to Call instructions in the SIL, hence we create MethodBody nodes to store these instructions.

Thanks for your patient answer! Make sense here.