Hi all,
Here I backport r227129 to branch 4.9 to fix exactly the same issue reported in
PR69082.
It's been already committed on trunk and backportted to branch 5.
I have quoted the original message for the explanation.
The patch applies to branch 4.9 without any modifications.
Test case is
On 12/01/16 15:31, Renlin Li wrote:
> Hi all,
>
> Here I backport r227129 to branch 4.9 to fix exactly the same issue
> reported in PR69082.
> It's been already committed on trunk and backportted to branch 5.
>
>
> I have quoted the original message for the explanation.
> The patch applies to
I have tested that, arm-none-linux-gnueabi bootstraps Okay on trunk code.
JFTR, this is ok to backport to gcc-5 in case there are no regressions.
regards
Ramana
Thanks,
Kyrill
On 20/08/15 09:36, Kyrylo Tkachov wrote:
On 19/08/15 12:49, Renlin Li wrote:
Hi all,
This simple patch will tighten the conditions when matching movw and
arm_movt rtx pattern.
Those two patterns will generate the following assembly:
movw w1, #:lower16: dummy + addend
movt w1, #:upper16:
Hi Renlin,
On 19/08/15 15:37, Renlin Li wrote:
Hi Kyrylo,
On 19/08/15 13:46, Kyrylo Tkachov wrote:
Hi Renlin,
Please send patches to gcc-patches for review.
Redirecting there now...
Thank you! I should really double check after Thunderbird auto complete
the address for me.
On
Hi Renlin,
Please send patches to gcc-patches for review.
Redirecting there now...
On 19/08/15 12:49, Renlin Li wrote:
Hi all,
This simple patch will tighten the conditions when matching movw and
arm_movt rtx pattern.
Those two patterns will generate the following assembly:
movw w1,
Hi Kyrylo,
On 19/08/15 13:46, Kyrylo Tkachov wrote:
Hi Renlin,
Please send patches to gcc-patches for review.
Redirecting there now...
Thank you! I should really double check after Thunderbird auto complete
the address for me.
On 19/08/15 12:49, Renlin Li wrote:
Hi all,
This simple
