Investigate the performance penalty of not using INLINABLE #51

tibbe opened this Issue Nov 9, 2012 · 0 comments


None yet
1 participant

tibbe commented Nov 9, 2012

By using INLINABLE we gain some performance benefits due to type specialization at the call-site. Since there are cases where the specialization might not trigger (i.e. due to compiler phase ordering issues) we should look at what the compiled code looks like without INLINABLE. Perhaps the core is looking worse than it has to in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment