"Vincent R." <foru...@smartmobili.com> writes:
> Yes I think I don't explain things very clearly, so what is important to
> know is that the __except keyword
> can be passed instructions(case 1) or directly a function(case 2).
I see that but I don't see why it matters.
> in the case 1) ie if you declare something like :
>
> ...
> __except( printf("hello gcc"), 1)
>
> and I look at asm generated I can notice that the instructions inside the
> patenthesis will be put inside a function
> because I can notice a prologue and epilogue.
What asm are you looking at?
gcc will do the right thing if you put statements in an exception
region.
> So on a arm plateform here is the annoted asm (asm + source code), I have
> only pasted the __except part :
I don't understand why the fact that some compiler generates a prologue
and epilogue implies anything about what gcc should do. The definition
of this language construct is presumably not written in terms of
prologues and epilogues. It is presumably written in terms of "execute
these statements, then do this."
Ian
