On Fri, Jul 22, 2016 at 12:19 AM, Jim Wilson wrote:
> On Thu, Jul 21, 2016 at 9:13 PM, Jeffrey Walton wrote:
>> So I guess the question is, what do I use for -mfpu=neon-vfp3 (or
>> -mfpu=neon-vfp3-d32)? Is -mfpu=neon enough?
>
> The -mfpu=neon option is enough. neon implies vfpv3 and 32 D regist
On Thu, Jul 21, 2016 at 9:13 PM, Jeffrey Walton wrote:
> So I guess the question is, what do I use for -mfpu=neon-vfp3 (or
> -mfpu=neon-vfp3-d32)? Is -mfpu=neon enough?
The -mfpu=neon option is enough. neon implies vfpv3 and 32 D registers.
Jim
___
li
On Thu, Jul 21, 2016 at 8:48 PM, Jeffrey Walton wrote:
> Is there an arm-msr-tools or similar that has setuid so we can access the
> MSRs?
I'm not familiar with any such tool, but I haven't looked for one
before. I found an x86 msr-tools project at github with a web search.
It seems to be a sta
On Thu, Jul 21, 2016 at 11:30 PM, Jim Wilson wrote:
> On Thu, Jul 21, 2016 at 6:33 PM, Jeffrey Walton wrote:
>> I think vfpd32 cpu flag means I have 32 D-registers. The cpu flags
>> neon and vfpv3 flags means I want something more than -mfpu=neon-fp16,
>> but I'm not sure what that is.
>
> neon i
On Thu, Jul 21, 2016 at 11:30 PM, Jim Wilson wrote:
> On Thu, Jul 21, 2016 at 6:33 PM, Jeffrey Walton wrote:
>> I think vfpd32 cpu flag means I have 32 D-registers. The cpu flags
>> neon and vfpv3 flags means I want something more than -mfpu=neon-fp16,
>> but I'm not sure what that is.
>
> neon i
On Thu, Jul 21, 2016 at 6:33 PM, Jeffrey Walton wrote:
> I think vfpd32 cpu flag means I have 32 D-registers. The cpu flags
> neon and vfpv3 flags means I want something more than -mfpu=neon-fp16,
> but I'm not sure what that is.
neon implies vfvp3 and 32 D-registers and asimd/neon support, so th
Hi Everyone,
I'm looking at the features of a BeagleBone Black. Its /proc/cpuinfo is below.
I think vfpd32 cpu flag means I have 32 D-registers. The cpu flags
neon and vfpv3 flags means I want something more than -mfpu=neon-fp16,
but I'm not sure what that is.
My question is, what GCC ARM option
On Thu, Jul 21, 2016 at 1:53 AM, Richard Earnshaw
wrote:
> On 20/07/16 22:33, Jim Wilson wrote:
>> On Wed, Jul 20, 2016 at 2:14 PM, Jeffrey Walton wrote:
>>> I'm having trouble with ARMv8/Aarch64. One is an early Mustang server
>>
>> ARMv8 implies 32-bit code (aarch32). Aaarch64 implies 64-bit c
On 20/07/16 22:33, Jim Wilson wrote:
> On Wed, Jul 20, 2016 at 2:14 PM, Jeffrey Walton wrote:
>> I'm having trouble with ARMv8/Aarch64. One is an early Mustang server
>
> ARMv8 implies 32-bit code (aarch32). Aaarch64 implies 64-bit code.
> These are two different compilers, with two different set
