[PATCH, ARM] Fix parsing of int/float immediates for Neon VMOV instructions
Paul Brook
paul@codesourcery.com
Fri Mar 2 17:56:00 GMT 2007
More information about the Binutils mailing list
Fri Mar 2 17:56:00 GMT 2007
- Previous message (by thread): [PATCH, ARM] Fix parsing of int/float immediates for Neon VMOV instructions
- Next message (by thread): [PATCH, ARM] Fix parsing of int/float immediates for Neon VMOV instructions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> To use floating-point immediates, you must now explicitly use a decimal > point or exponent, i.e. > > vmov.f32 dX, #10.0 > > not > > vmov.f32 dX, #10 This would be ok if we rejected the latter. However IIUC after your patch we silently encode the latter as vmov.i32 dX, #10. This is equivalent to vmov.f32 dX, #<some denormal or unrepresentable FP value> which is almost certainly not what the user intended. Paul
- Previous message (by thread): [PATCH, ARM] Fix parsing of int/float immediates for Neon VMOV instructions
- Next message (by thread): [PATCH, ARM] Fix parsing of int/float immediates for Neon VMOV instructions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Binutils mailing list