|
|||
| Products Download Events Support Videos | |||
Technical Support
On-Line Manuals
Migration and Compatibility
Conventions and feedback
Migrating from ARM Compiler v4.1 for µVision
Migrating from RVCT v4.0 for µVision to ARM C
Migrating from RVCT v3.1 for µVision to RVCT
General changes between RVCT v3.1 for µVision
Changes to symbol visibility between RVCT v3.1 for
Compiler changes between RVCT v3.1 for µVisio
Linker changes between RVCT v3.1 for µVision
Assembler changes between RVCT v3.1 for µVisi
fromelf changes between RVCT v3.1 for µVision
C and C++ library changes between RVCT v3.1 for &#
Migration and Compatibility
General changes between RVCT v3.1 for µVision and RVCT v4.0 for µVision
| |||
| Home > Migrating from RVCT v3.1 for µVision to RVCT v4.0 for µVision > General changes between RVCT v3.1 for µVision and RVCT v4.0 for µVision | |||
The following changes affect multiple tools:
Restrictions on --fpu--fpu=VFPv2 or --fpu=VFPv3 are
only accepted if CPU architecture is greater than or equal to ARMv5TE.
This affects all tools that accept --fpu.
Note
The assembler assembles VFP instructions when you use the --unsafe option,
so do not use --fpu when using --unsafe.
If you use --fpu with --unsafe,
the assembler downgrades the reported architecture error to a warning.
The following --cpu choices are obsolete
and have been removed:
5
5E
5ExP
5EJ
5EWMMX2
5EWMMX
5TEx
ARM9E-S-rev0
ARM946E-S-rev0
ARM966E-S-rev0.
- Reference
Compiler Reference:
Linker Reference:
Assembler Reference:
| Copyright © 2011-2012 ARM. All rights reserved. | ARM DUI 0593B |
| Non-Confidential | ID062912 |
 PDF version | |
| Home > Migrating from RVCT v3.1 for µVision to RVCT v4.0 for µVision > General changes between RVCT v3.1 for µVision and RVCT v4.0 for µVision |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Contact |
|
 |
|||
