Excerpts from Richard Sandiford's message of August 19, 2020 1:22 pm:
> Iain Buclaw via Gcc-patches writes:
>> Hi,
>>
>> On x86, a memory reference reference to a TLS address can be broken out
>> and stored in a register, for instance:
>>
>> movq %fs:8+testYearsBC@tpoff, %rdx
>>
>>
Iain Buclaw via Gcc-patches writes:
> Hi,
>
> On x86, a memory reference reference to a TLS address can be broken out
> and stored in a register, for instance:
>
> movq %fs:8+testYearsBC@tpoff, %rdx
>
> Subsequently becomes:
>
> pushq %rbp
> leaq 8+testYearsBC@tpoff,
Ping.
Though I wonder if there's any point adding a check at all over just swapping
the order that mem_loc_descriptor and tls_mem_loc_descriptor are called in.
Iain.
On 07/08/2020 13:33, Iain Buclaw wrote:
> Hi,
>
> On x86, a memory reference reference to a TLS address can be broken out
> and
Hi,
On x86, a memory reference reference to a TLS address can be broken out
and stored in a register, for instance:
movq%fs:8+testYearsBC@tpoff, %rdx
Subsequently becomes:
pushq %rbp
leaq8+testYearsBC@tpoff, %rbp
// later...
movq%fs:0(%rbp),
