"Vincent R." <foru...@smartmobili.com> writes: > Once again what I describe above is simplified because when seh is used, > there is a mechanism > called virtual unwiding that I didn't explained but that is the reason to > store the prologue length.
It's worth noting that in gcc the "prologue length" is normally an undefined concept. gcc can and will schedule prologue instructions interleaved with non-prologue instructions. This can be prevented by using a blockage instruction, at the cost of some runtime performance. Ian
