Displaying 7 results from an estimated 7 matches for "targetglobaltlsaddress".
2017 Feb 07
3
[cfe-dev] lli: LLVM ERROR: Cannot select: X86ISD::WrapperRIP TargetGlobalTLSAddress:i64
...e
TLS in the name).
>
> The same result can be reproduced by this simple program:
>
> thread_local int x = 0;
> int main() {
> return 0;
> }
>
>When compiled into IR it produces similar error:
>
>LLVM ERROR: Cannot select: t19: i64 = X86ISD::WrapperRIP
TargetGlobalTLSAddress:i64<i32* @x> 0 [TF=19]
> t18: i64 = TargetGlobalTLSAddress<i32* @x> 0 [TF=19]
>In function: _ZTW1x
interestingly this works on my machine.
llvm-ir attached
2017-02-07 15:31 GMT+00:00 Alex Denisov <1101.debian at gmail.com>:
> I’ve seen the same problem, but didn’t...
2017 Feb 07
2
[cfe-dev] lli: LLVM ERROR: Cannot select: X86ISD::WrapperRIP TargetGlobalTLSAddress:i64
...main.cpp && lli main.ll on Linux(Debian)
>
> #include <future>
>
> int main () {
> return std::async([]{return 1;}).get();
> }
> fails to run on lli due to the following error:
>
> LLVM ERROR: Cannot select: 0xd012e0:
> i64 = X86ISD::WrapperRIP TargetGlobalTLSAddress:i64<i8** @_ZSt15__once_callable> 0 [TF=10]
>
> 0xd020c0: i64 = TargetGlobalTLSAddress<i8** @_ZSt15__once_callable> 0 [TF=10]
> In function: _ZSt9call_onceIMNSt13__future_base13_State_baseV2EFvPSt8functionIFSt10unique_ptrINS0_12_Result_baseENS4_8_DeleterEEvEEPbEJPS1_S9_SA_EEvR...
2017 Feb 08
2
[cfe-dev] lli: LLVM ERROR: Cannot select: X86ISD::WrapperRIP TargetGlobalTLSAddress:i64
...t;> >
>> > thread_local int x = 0;
>> > int main() {
>> > return 0;
>> > }
>> >
>> >When compiled into IR it produces similar error:
>> >
>> >LLVM ERROR: Cannot select: t19: i64 = X86ISD::WrapperRIP
>> TargetGlobalTLSAddress:i64<i32* @x> 0 [TF=19]
>> > t18: i64 = TargetGlobalTLSAddress<i32* @x> 0 [TF=19]
>> >In function: _ZTW1x
>>
>> interestingly this works on my machine.
>>
>> llvm-ir attached
>>
>>
>>
>> 2017-02-07 15:31 GMT+00:00 Alex De...
2018 Apr 22
0
[cfe-dev] lli: LLVM ERROR: Cannot select: X86ISD::WrapperRIP TargetGlobalTLSAddress:i64
Over one year passed now, did anybody made any progress regarding this
issue?
On 9 February 2017 at 16:33, Gaetano Checinski <gaetano.checinski at gmail.com>
wrote:
> I'm looking currently into a patch
>
2017 Feb 08
0
[cfe-dev] lli: LLVM ERROR: Cannot select: X86ISD::WrapperRIP TargetGlobalTLSAddress:i64
[Adding llvm-dev back to list]
On 8 February 2017 at 11:12, Gaetano Checinski
<gaetano.checinski at gmail.com> wrote:
> Thanks for sharing your insights,
> so in theory i could build an llvm pass that calls TargetLowering::LowerToTLSEmulatedModel for each llvm::Function and it should work if i link a runtime that provides __emultls_get_address.
I'm afraid not, that function is
2017 Feb 09
1
[cfe-dev] lli: LLVM ERROR: Cannot select: X86ISD::WrapperRIP TargetGlobalTLSAddress:i64
I'm looking currently into a patch
<https://mailtrack.io/trace/link/60b02baa5e1b3d7ffe6fbb428b343be17c58c583?url=https%3A%2F%2Fgithub.com%2FJuliaLang%2Fllvm%2Fcommit%2Fa9e17b7f47f5afa9683fc8cfeff7020b2ff4a8b2%23diff-0fa8ca8690e36a8dfd05f6b751955164R339&signature=222c65b9d92c011f>
which has been written for JuliaLang and is supposed to fix TLS for linux.
Unfortunately it is based on
2017 Feb 08
3
[cfe-dev] lli: LLVM ERROR: Cannot select: X86ISD::WrapperRIP TargetGlobalTLSAddress:i64
> Unfortunately it doesn't look like lli has support for emulated TLS either,
though that would be pretty simple to add.
As an experiment I've `llvm::createLowerEmuTLSPass` into lli which
added @__emutls_v.x and @__emutls_v.t.
However i didn't have any __emultls_get_address calls in my IR.
Is there a llvm pass or compiler-flag that replaces thread_locals with
appropriate