[llvm-commits] [patch] Change how we handle mandatory unwind tables

Rafael Ávila de Espíndola rafael.espindola at gmail.com
Mon May 23 12:59:44 PDT 2011


On 2011-05-23 15:51, Renato Golin wrote:
> 2011/5/23 Rafael Ávila de Espíndola <rafael.espindola at gmail.com>:
>> Adding this to TargetData is a bit strange, but I am not sure where else
>> to put it.
> 
> The first thing I thought when reading until here was to add another
> function attribute...
> 
> 
>> The prune-eh issue can be fixed by adding a new attribute, noehframe.
>> With the new attribute nounwind would keep its current meaning of "no
>> exception will unwind past this" and noehframe would be the more strict
>> "nothing (debuggers, profilers) will try to unwind past this".
> 
> Which is what you propose here...
> 
> Doesn't that fix the whole problem without the need to add bits to TargetData?

The bit in TargetData would be to allow eh-prune to set nounwind (or
noehframe if we add it). Thinking about it a bit more, I don't think
there would ever be the need to set noehframe once the FE is done. I
will give it a try and see what it looks like.

> cheers,
> --renato

Cheers,
Rafael



More information about the llvm-commits mailing list