Hi Thomas,
On 18/04/18 12:31, Thomas Preudhomme wrote:
Hi Kyrill,
On 11/04/18 10:02, Kyrill Tkachov wrote:
Hi Thomas,
On 09/04/18 15:29, Thomas Preudhomme wrote:
Hi Ramana,
On 06/04/18 17:17, Thomas Preudhomme wrote:
>
>
> On 06/04/18 17:08, Ramana Radhakrishnan wrote:
>> On 06/04/2018
Hi Kyrill,
On 11/04/18 10:02, Kyrill Tkachov wrote:
Hi Thomas,
On 09/04/18 15:29, Thomas Preudhomme wrote:
Hi Ramana,
On 06/04/18 17:17, Thomas Preudhomme wrote:
>
>
> On 06/04/18 17:08, Ramana Radhakrishnan wrote:
>> On 06/04/2018 16:54, Thomas Preudhomme wrote:
>>> Instruction pattern for
Hi Thomas,
On 09/04/18 15:29, Thomas Preudhomme wrote:
Hi Ramana,
On 06/04/18 17:17, Thomas Preudhomme wrote:
>
>
> On 06/04/18 17:08, Ramana Radhakrishnan wrote:
>> On 06/04/2018 16:54, Thomas Preudhomme wrote:
>>> Instruction pattern for setting the FPSCR expects the input value to be
>>> in
Hi Ramana,
On 06/04/18 17:17, Thomas Preudhomme wrote:
On 06/04/18 17:08, Ramana Radhakrishnan wrote:
On 06/04/2018 16:54, Thomas Preudhomme wrote:
Instruction pattern for setting the FPSCR expects the input value to be
in a register. However, __builtin_arm_set_fpscr expander does not
On 06/04/18 17:08, Ramana Radhakrishnan wrote:
On 06/04/2018 16:54, Thomas Preudhomme wrote:
Instruction pattern for setting the FPSCR expects the input value to be
in a register. However, __builtin_arm_set_fpscr expander does not ensure
that this is the case and as a result GCC ICEs when the
On 06/04/2018 16:54, Thomas Preudhomme wrote:
> Instruction pattern for setting the FPSCR expects the input value to be
> in a register. However, __builtin_arm_set_fpscr expander does not ensure
> that this is the case and as a result GCC ICEs when the builtin is
> called with a constant literal.
Instruction pattern for setting the FPSCR expects the input value to be
in a register. However, __builtin_arm_set_fpscr expander does not ensure
that this is the case and as a result GCC ICEs when the builtin is
called with a constant literal.
This commit fixes the builtin to force the input
