Clang doesn't know about the static code, so it can't do the optimizations this does.
You could probably do the same thing with some hacky C++ code gen and templates, but I'm not sure clang et al would be able to optimize them.
You could probably do the same thing with some hacky C++ code gen and templates, but I'm not sure clang et al would be able to optimize them.
that is the whole point of jitter
The other thing C&P does is allow for a library of stencils and stitch them together intelligently depending on where arguments are coming from, where the return should go, where the flow of control should go next, etc
EDIT: So I guess they look fairly similar, huh
fwiw i thought this was a stupid, hacky, pointless approach when it was called jitter and i still think it's a stupid, hacky, pointless approach when it's called copy-and-patch ;)
but still like to see credit where it's due