[LLVMdev] Why does "uwtable" prevent optimizing Invoke -> Call?

Reid Kleckner rnk at google.com
Thu Jan 22 12:45:10 PST 2015


I went ahead and reverted this in r226850 after some discussion on IRC.

On Thu, Jan 22, 2015 at 9:46 AM, Reid Kleckner <rnk at google.com> wrote:

> On Thu, Jan 22, 2015 at 4:40 AM, Björn Steinbrink <bsteinbr at gmail.com>
> wrote:
>
>> On 2015.01.22 10:42:51 +0100, Björn Steinbrink wrote:
>> > an effect on that function call. So AFAICT either I'm missing something
>> > here, or clang should always emit invoke, disabling the optimization for
>> > functions that have the uwtable attribute was wrong and the change
>> > should be reverted.
>>
>> I meant to write "either I'm missing something, or clang should always
>> emit invoke instructions _or_ disabling the optimization was wrong".
>
>
> I agree, I don't see how uwtable has anything to do with this
> optimization. There must be something wrong with our CFI instead.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20150122/41f76dbe/attachment.html>


More information about the llvm-dev mailing list