Since this is a bug fix, I'll need to backport to 4.8.
Is that OK?
Cheers,
Ian
OK
/Marcus
On 20 March 2013 17:21, Ian Bolton ian.bol...@arm.com wrote:
MOVK should not be generated with a negative immediate, which
the assembler rightfully rejects.
This patch makes MOVK output its
On 25/04/13 16:38, Ian Bolton wrote:
Since this is a bug fix, I'll need to backport to 4.8.
Is that OK?
Cheers,
Ian
OK
/Marcus
On 20 March 2013 17:21, Ian Bolton ian.bol...@arm.com wrote:
MOVK should not be generated with a negative immediate, which
the assembler rightfully rejects.
This
On 20/03/13 17:21, Ian Bolton wrote:
MOVK should not be generated with a negative immediate, which
the assembler rightfully rejects.
This patch makes MOVK output its 2nd operand in hex instead.
Tested on bare-metal and linux.
OK for trunk?
Cheers,
Ian
2013-03-20 Ian Bolton
OK
/Marcus
On 20 March 2013 17:21, Ian Bolton ian.bol...@arm.com wrote:
MOVK should not be generated with a negative immediate, which
the assembler rightfully rejects.
This patch makes MOVK output its 2nd operand in hex instead.
Tested on bare-metal and linux.
OK for trunk?
Cheers,
Ian
MOVK should not be generated with a negative immediate, which
the assembler rightfully rejects.
This patch makes MOVK output its 2nd operand in hex instead.
Tested on bare-metal and linux.
OK for trunk?
Cheers,
Ian
2013-03-20 Ian Bolton ian.bol...@arm.com
gcc/
*