On 04/05/17 11:08, Marek Polacek wrote:
> Ping.
>
> On Thu, Apr 27, 2017 at 12:44:42PM +0200, Marek Polacek wrote:
>> This is a backport of the ARM ABI fix, except that it doesn't change code,
>> only adds the ABI warning.
>>
>> So there were four changes, three of them are changing "else if (res
Ping.
On Thu, Apr 27, 2017 at 12:44:42PM +0200, Marek Polacek wrote:
> This is a backport of the ARM ABI fix, except that it doesn't change code,
> only adds the ABI warning.
>
> So there were four changes, three of them are changing "else if (res < 0)"
> to "if (res != 0)" and the fourth was
On Thu, Apr 27, 2017 at 02:46:23PM +0200, Jakub Jelinek wrote:
> On Thu, Apr 27, 2017 at 01:37:02PM +0100, Richard Earnshaw (lists) wrote:
> > > + if (ncrn & 1)
> > > +{
> > > + int res = arm_needs_doubleword_align (mode, type);
> > > + /* Only warn during RTL expansion of call
On Thu, Apr 27, 2017 at 01:37:02PM +0100, Richard Earnshaw (lists) wrote:
> > + if (ncrn & 1)
> > +{
> > + int res = arm_needs_doubleword_align (mode, type);
> > + /* Only warn during RTL expansion of call stmts, otherwise we would
> > +warn e.g. during gimplification even on
On 27/04/17 11:44, Marek Polacek wrote:
> This is a backport of the ARM ABI fix, except that it doesn't change code,
> only adds the ABI warning.
>
> So there were four changes, three of them are changing "else if (res < 0)"
> to "if (res != 0)" and the fourth was the "res != 0" change in
>
This is a backport of the ARM ABI fix, except that it doesn't change code,
only adds the ABI warning.
So there were four changes, three of them are changing "else if (res < 0)"
to "if (res != 0)" and the fourth was the "res != 0" change in
arm_function_arg_boundary.
I've verified on a testcase
