On 17/10/13 13:46, Sebastian Huber wrote:
> On 2013-10-17 14:24, Richard Earnshaw wrote:
>> On 17/10/13 08:56, Joey Ye wrote:
There is no macro to indicate VFP variances. Probably you can check
CPU variance instead. As I know Cortex-R only support D16.
>> Checking __ARM_ARCH_PROFILE
On 2013-10-17 14:24, Richard Earnshaw wrote:
On 17/10/13 08:56, Joey Ye wrote:
>There is no macro to indicate VFP variances. Probably you can check
>CPU variance instead. As I know Cortex-R only support D16.
>
Checking __ARM_ARCH_PROFILE == 'R' would tell you that it's R profile
and therefore o
On 17/10/13 08:56, Joey Ye wrote:
> There is no macro to indicate VFP variances. Probably you can check
> CPU variance instead. As I know Cortex-R only support D16.
>
Checking __ARM_ARCH_PROFILE == 'R' would tell you that it's R profile
and therefore only 16 regs.
R.
> Joey
>
> On Thu, Oct 17,
There is no macro to indicate VFP variances. Probably you can check
CPU variance instead. As I know Cortex-R only support D16.
Joey
On Thu, Oct 17, 2013 at 3:47 PM, Sebastian Huber
wrote:
> On 2013-10-17 09:28, Joey Ye wrote:
>>
>> Which Cortex-R you are targeting that supports both D16 and D32?
On 2013-10-17 09:28, Joey Ye wrote:
Which Cortex-R you are targeting that supports both D16 and D32?
I have a Cortex-R variant which supports D16 only and now I want to add a
multi-lib to our GCC target configuration and use a compiler built-in to adjust
the context switch code for this multi
Which Cortex-R you are targeting that supports both D16 and D32?
Thanks,
Joey
On Thu, Oct 17, 2013 at 3:13 PM, Sebastian Huber
wrote:
> Hello,
>
> it seems that it is not possible to deduce from GCC built-in defines whether
> we compile for the VFPv3-D16 or VFPv3-D32 floating point unit.
>
> tou
