You copied the Doc URL to your clipboard.

Arm Compiler Migration and Compatibility Guide : Summary of changes between Arm Compiler 6.8 and Arm Compiler 6.9

Summary of changes between Arm® Compiler 6.8 and Arm® Compiler 6.9

summary of the changes between Arm® Compiler 6.8 and Arm Compiler 6.9.

General changes

The following are general changes in Arm Compiler 6.9:

  • Added support for the Armv8.4-A architecture. To target Armv8.4-A, use the following options:
    State armclang options armlink, and fromelf options
    AArch64 --target=aarch64-arm-none-eabi -march=armv8.4-a Do not use the --cpu=name option.
    AArch32 --target=arm-arm-none-eabi -march=armv8.4-a Do not use the --cpu=name option.

    Note

    The legacy assembler, armasm, does not support the Armv8.4-A architecture.
  • Added support for the optional Cryptographic Extension in Armv8.4-A. To target Armv8.4-A with the Cryptographic Extension, use the following options:
    State armclang options armlink and fromelf options
    AArch64 --target=aarch64-arm-none-eabi -march=armv8.4-a+crypto Do not use the --cpu=name option.
    AArch32 --target=arm-arm-none-eabi -march=armv8.4-a -mfpu=crypto-neon-fp-armv8 Do not use the --cpu=name option.

    Note

    The legacy assembler, armasm, does not support the Armv8.4-A architecture.

    For more information about selecting specific cryptographic algorithms, see -mcpu in the armclang Reference Guide.

  • change in Arm Compiler 6.9 means that compiling with -mexecute-only always generates an empty .text section that is read-only.

    For more information about handling this section, see Compiling with -mexecute-only generates an empty .text section.

Was this page helpful? Yes No