[llvm-commits] [PATCH] Incorrect VFP version supporting ARM Cortex-M4

Renato Golin rengolin at systemcall.org
Fri Jul 27 04:01:33 PDT 2012


On 27 July 2012 03:12, Jiangning Liu <jiangning.liu at arm.com> wrote:
> Hopefully this can answer your question.

Maybe indirectly, it does. If I got it right, they're named
differently (S16 vs. D32) to be able to do the same thing differently,
though the major name (VFPv4) is the same, to allow us to infer that
most instructions will be the same (single-precision ones, that is).

I think, from a global point of view, it's safe to assume S16 == (D32
- double-precision instructions), and whatever difference can be coded
as a new SP-only instruction, enabled by the FeatureVFPOnlySP flag.

Jiangning, from a historical point of view, I think it'd be safer to
add the FeatureVFPOnlySP flag now, even if inactive, so that people
don't assume anything when adding instructions to VFPv4. Jim, do you
think that'd be overkill?

-- 
cheers,
--renato

http://systemcall.org/



More information about the llvm-commits mailing list