Jiong Wang writes:
> Andrew Pinski writes:
>
>> On Tue, Jul 28, 2015 at 6:12 AM, Jiong Wang wrote:
>>>
>>> The instruction sequences for preparing argument for TLS descriptor
>>> runtime resolver and the later function call to resolver can actually be
>>> hoisted out of the loop.
>>>
>>> Current
On 28 July 2015 at 14:12, Jiong Wang wrote:
>
> The instruction sequences for preparing argument for TLS descriptor
> runtime resolver and the later function call to resolver can actually be
> hoisted out of the loop.
>
> Currently we can't because we have exposed the hard register X0 as
> destina
Andrew Pinski writes:
> On Tue, Jul 28, 2015 at 6:12 AM, Jiong Wang wrote:
>>
>> The instruction sequences for preparing argument for TLS descriptor
>> runtime resolver and the later function call to resolver can actually be
>> hoisted out of the loop.
>>
>> Currently we can't because we have ex
On Fri, Sep 25, 2015 at 11:40 PM, Andrew Pinski wrote:
> On Tue, Jul 28, 2015 at 6:12 AM, Jiong Wang wrote:
>>
>> The instruction sequences for preparing argument for TLS descriptor
>> runtime resolver and the later function call to resolver can actually be
>> hoisted out of the loop.
>>
>> Curre
On Tue, Jul 28, 2015 at 6:12 AM, Jiong Wang wrote:
>
> The instruction sequences for preparing argument for TLS descriptor
> runtime resolver and the later function call to resolver can actually be
> hoisted out of the loop.
>
> Currently we can't because we have exposed the hard register X0 as
>
Andreas Schwab writes:
> Jiong Wang writes:
>
>> I Just finished several round of rebuild & testing on clean
>> environment.
>
> How did you even manage to compile it?
>
> ../../gcc/ira.c: In function 'void print_translated_classes(FILE*, bool)':
> ../../gcc/ira.c:1415:49: error: iteration 8
Andreas Schwab writes:
> Jiong Wang writes:
>
>> I Just finished several round of rebuild & testing on clean
>> environment.
>
> How did you even manage to compile it?
>
> ../../gcc/ira.c: In function 'void print_translated_classes(FILE*, bool)':
> ../../gcc/ira.c:1415:49: error: iteration 8
Jiong Wang writes:
> I Just finished several round of rebuild & testing on clean
> environment.
How did you even manage to compile it?
../../gcc/ira.c: In function 'void print_translated_classes(FILE*, bool)':
../../gcc/ira.c:1415:49: error: iteration 8u invokes undefined behavior
[-Werror
Andreas Schwab writes:
> Jiong Wang writes:
>
>> Andreas Schwab writes:
>>
>>> Jiong Wang writes:
>>>
And I just finished two round of native aarch64 build/check w/wo my patch.
>>>
>>> Did you rebuild everything?
>>
>> No.
>
> Please do.
Andreas,
I Just finished several round of rebuil
Jiong Wang writes:
> Andreas Schwab writes:
>
>> Jiong Wang writes:
>>
>>> And I just finished two round of native aarch64 build/check w/wo my patch.
>>
>> Did you rebuild everything?
>
> No.
Please do.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 94
Andreas Schwab writes:
> Jiong Wang writes:
>
>> And I just finished two round of native aarch64 build/check w/wo my patch.
>
> Did you rebuild everything?
No.
Just applied the patch, then "make all" and re-check
>
> Andreas.
--
Regards,
Jiong
Jiong Wang writes:
> And I just finished two round of native aarch64 build/check w/wo my patch.
Did you rebuild everything?
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Jiong Wang writes:
> Andreas Schwab writes:
>
>> Jiong Wang writes:
>>
>>> Index: gcc/ChangeLog
>>> ===
>>> --- gcc/ChangeLog (revision 226682)
>>> +++ gcc/ChangeLog (working copy)
>>> @@ -1,3 +1,16 @@
>>> +2015-08-06Ramana
Andreas Schwab writes:
> Jiong Wang writes:
>
>> Index: gcc/ChangeLog
>> ===
>> --- gcc/ChangeLog(revision 226682)
>> +++ gcc/ChangeLog(working copy)
>> @@ -1,3 +1,16 @@
>> +2015-08-06Ramana Radhakrishnan
>> +
Jiong Wang writes:
> Index: gcc/ChangeLog
> ===
> --- gcc/ChangeLog (revision 226682)
> +++ gcc/ChangeLog (working copy)
> @@ -1,3 +1,16 @@
> +2015-08-06Ramana Radhakrishnan
> + Jiong Wang
> +
> + * conf
James Greenhalgh writes:
> On Tue, Jul 28, 2015 at 02:12:36PM +0100, Jiong Wang wrote:
>>
>> The instruction sequences for preparing argument for TLS descriptor
>> runtime resolver and the later function call to resolver can actually be
>> hoisted out of the loop.
>>
>> Currently we can't becau
On Tue, Jul 28, 2015 at 02:12:36PM +0100, Jiong Wang wrote:
>
> The instruction sequences for preparing argument for TLS descriptor
> runtime resolver and the later function call to resolver can actually be
> hoisted out of the loop.
>
> Currently we can't because we have exposed the hard registe
The instruction sequences for preparing argument for TLS descriptor
runtime resolver and the later function call to resolver can actually be
hoisted out of the loop.
Currently we can't because we have exposed the hard register X0 as
destination of "set". While GCC's RTL data flow infrastructure
18 matches
Mail list logo
