3 ms·
I'm surprised that cache sizes and jump distance were not mentioned. Would that mean the size reduction is good enough that we're safely ignoring potential fetc
by viraptor 6y ago
I'm surprised that cache sizes and jump distance were not mentioned. Would that mean the size reduction is good enough that we're safely ignoring potential fetch of another page of code?
- cesaref 6y agoYes, I noticed this omission. It would be helpful to at least discuss the performance implications of this. I imagine the target audience are compiling for limited memory embedded devices where reducing the memory pressure could allow a cheaper SoC to be used where performance is not a concern. From a performance perspective, I was wondering how this would interact with inlining, as there is the potential to inline and then extract more generalised call sequences and hence get better performance without the memory bloat from inlining. Definitely sounds like an interesting option.
- yroux 6y agoYes that's it, I wanted to put the focus on code size but maybe I should have said a word about performance as well. I replied to the speed question in a previous comment, but can put it here as well, I don't have exact numbers to report but on average you can expect a regression around 2%, but it will depend of call latency of the core and is also impacted by cache effects, so in some cases you can have a performance improvement
- yroux 6y agoThe focus is pure code size reduction here and it doesn't look at the cache locality or performance which might be improved if the size reduction avoids some i-cache misses or not but that's a price to pay.
- wyldfire 6y agoWith a code size reduction like this, I'd expect an icache hit ratio improvement. But to your point - do we have to add more trampolines to critical paths? If so it might not be a net performance improvement. The fact that so many other architectures enable it seem to hint that it would likely pay off for arm-32 too.