llvm dev - Dec 2015 - [PPC64] mflr gets scheduled after __tls_get_addr call

Hi,

I got a minimized test case that's causing miscompiled TLS initialization
code: https://gist.github.com/innocentim/939ebbff1e312801bafe

Should I just insert PPC::STACKCALLDOWN AND PPC::STACKCALLUP
into ppc-tls-dynamic-call? I'm not quite sure if the frame size is simply 0?

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151215/f33e2053/attachment.html>

On Tue, Dec 15, 2015 at 1:42 PM Tim Shen <timshen at google.com> wrote:
> Hi,
>
> I got a minimized test case that's causing miscompiled TLS
initialization
> code: https://gist.github.com/innocentim/939ebbff1e312801bafe
>
> Should I just insert PPC::STACKCALLDOWN AND PPC::STACKCALLUP
> into ppc-tls-dynamic-call? I'm not quite sure if the frame size is
simply 0?
>
Sorry, they are PPC::ADJCALLSTACKDOWN and PPC::ADJCALLSTACKUP.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20151215/cbd07749/attachment.html>

You should probably open a bug report.

Cheers,
Rafael


On 15 December 2015 at 16:42, Tim Shen via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Hi,
>
> I got a minimized test case that's causing miscompiled TLS
initialization
> code: https://gist.github.com/innocentim/939ebbff1e312801bafe
>
> Should I just insert PPC::STACKCALLDOWN AND PPC::STACKCALLUP into
> ppc-tls-dynamic-call? I'm not quite sure if the frame size is simply 0?
>
> Thanks!
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>