Arm Compiler 6.20 迁移与兼容性指南

需积分: 5 23 浏览量更新于2024-06-22 收藏 1.21MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

"Arm Compiler for Embedded Version 6.20 迁移和兼容性指南，由ARM Limited或其子公司版权所有，包含从版本6.13到6.18的更新历史，提供关于ARM编译器在不同版本间的迁移和兼容性指导。" 本文档是ARM公司针对其嵌入式领域的编译器——ARM Compiler的一份迁移和兼容性指南，适用于版本6.20。这份指南主要目的是帮助开发者理解如何在不同版本的ARM Compiler之间进行代码迁移，并确保代码的兼容性。一、版本历史与变更自2019年以来，ARM Compiler经历了多次版本更新，包括： 1. 版本6.13：2019年10月9日发布，是非机密版本，标志着该系列编译器的起点。 2. 版本6.14：2020年2月26日发布，同样是非机密版本，带来了新的功能和改进。 3. 版本6.15：2020年10月7日发布，后续还有12月14日的文档更新1，增强了编译器的性能和稳定性。 4. 版本6.16：2021年3月3日发布，3月12日的文档更新1提供了额外的技术细节和修复。 5. 版本6.17：2021年10月20日发布，继续优化编译器的性能和兼容性。 6. 版本6.18：2022年3月22日发布，这是最新的公开版本，可能包含了更多新特性和优化。每次版本更新通常会包含性能提升、错误修复、新特性添加以及对现有特性的改进，这些变化可能影响代码的编译和执行，因此迁移和兼容性指南显得尤为重要。二、代码迁移代码迁移涉及到将基于旧版本ARM Compiler编写的代码转换到新版本中。这可能涉及到以下步骤： 1. 了解新版本的变化：开发者首先需要熟悉新版本编译器引入的新特性、工具链的更新以及可能的API变动。 2. 代码审查：检查源代码，识别可能因版本升级而引发问题的部分，如已废弃的函数或不兼容的语法。 3. 适配修改：根据新版本的要求调整代码，以确保其能在新编译器下正确编译和运行。 4. 测试验证：在新编译器环境下进行充分的测试，确保代码功能完整且性能稳定。三、兼容性问题兼容性问题通常涉及代码在不同版本编译器下的一致性。指南可能涵盖以下方面： 1. 兼容性模式：某些编译器可能提供兼容模式，允许代码在新版本中保持与旧版本相似的行为。 2. 兼容性问题列表：列出已知的兼容性问题，以及解决这些问题的建议和方法。 3. 标准库和API兼容性：新版本可能会更新或移除部分库函数和API，需要确认代码中的调用是否受影响。 4. 目标平台兼容性：编译器更新可能影响支持的目标硬件平台，确保代码在目标设备上的兼容性。四、迁移策略为了平稳过渡，开发者应采取以下策略： 1. 分阶段迁移：逐步将代码库的一部分迁移到新版本，以便更轻松地管理和调试问题。 2. 制定计划：创建详细的迁移计划，包括时间表、任务分配和预期的挑战。 3. 文档记录：记录迁移过程中的问题和解决方案，为未来的迁移提供参考。五、总结 ARM Compiler的迁移和兼容性指南为开发者提供了宝贵的资源，帮助他们顺利过渡到新版本，保持代码的稳定性和兼容性。通过理解和遵循这份指南，开发团队可以减少迁移过程中的不确定性，确保项目持续高效地进行。

资源详情

资源推荐

Arm

Compiler for Embedded Migration and Compatibility

Guide

Document ID: 100068_6.20_00_en

Version 6.20

Conﬁguration and Support Information

•

Arm encourages the use of beta product features, and welcomes feedback on them.

•

Any issues with beta product features that Arm encounters or is made aware of are

considered for ﬁxing in future versions of Arm Compiler for Embedded.

Alpha product features

Alpha product features are not implementation complete, and are subject to change in future

releases, therefore the stability level is lower than in beta product features.

Alpha product features are identiﬁed with [ALPHA].

•

Arm endeavors to document known limitations of alpha product features.

•

Arm encourages the use of alpha product features, and welcomes feedback on them.

•

Any issues with alpha product features that Arm encounters or is made aware of are

considered for ﬁxing in future versions of Arm Compiler for Embedded.

Community features

Arm Compiler for Embedded 6 is built on LLVM technology and preserves the functionality of that

technology where possible. This means that there are additional features available in Arm Compiler

for Embedded that are not listed in the documentation. These additional features are known as

community features. For information on these community features, see the Clang Compiler User's

Manual.

Where community features are referenced in the documentation, they are identiﬁed with

[COMMUNITY].

•

Arm makes no claims about the quality level or the degree of functionality of these features,

except when explicitly stated in this documentation.

•

Functionality might change signiﬁcantly between feature releases.

•

Arm makes no guarantees that community features will remain functional across update

releases, although changes are expected to be unlikely.

Some community features might become product features in the future, but Arm provides no

roadmap for this. Arm is interested in understanding your use of these features, and welcomes

feedback on them. Arm supports customers using these features on a best-eﬀort basis, unless the

features are unsupported. Arm accepts defect reports on these features, but does not guarantee

that these issues will be ﬁxed in future releases.

Guidance on use of community features

There are several factors to consider when assessing the likelihood of a community feature being

functional:

•

The following ﬁgure shows the structure of the Arm Compiler for Embedded 6 toolchain:

Non-Conﬁdential

Page 16 of 146

Arm

Compiler for Embedded Migration and Compatibility

Guide

Document ID: 100068_6.20_00_en

Version 6.20

Conﬁguration and Support Information

•

The Clang implementations of compiler features, particularly those that have been present for a

long time in other toolchains, are likely to be mature. The functionality of new features, such as

support for new language features, is likely to be less mature and therefore more likely to have

limited functionality.

Deprecated features

A deprecated feature is one that Arm plans to remove from a future release of Arm Compiler for

Embedded. Arm does not make any guarantee regarding the testing or maintenance of deprecated

features. Therefore, Arm does not recommend using a feature after it is deprecated.

For information on replacing deprecated features with supported features, see the Arm Compiler

for Embedded documentation and Release Notes. Where appropriate, each Arm Compiler

document includes notes for features that are deprecated, and also provides entries in the changes

appendix of that document.

Unsupported features

With both the product and community feature categories, speciﬁc features and use-cases are

known not to function correctly, or are not intended for use with Arm Compiler for Embedded 6.

Limitations of product features are stated in the documentation. Arm cannot provide an exhaustive

list of unsupported features or use-cases for community features. The known limitations on

community features are listed in Community features.

List of known unsupported features

The following is an incomplete list of unsupported features, and might change over time:

•

The Clang option -stdlib=libstdc++ is not supported.

•

C++ static initialization of local variables is not thread-safe when linked against the standard

C++ libraries. For thread-safety, you must provide your own implementation of thread-safe

functions as described in Standard C++ library implementation deﬁnition.

This restriction does not apply to the [ALPHA]-supported multithreaded C++

libraries.

•

Use of C11 library features is unsupported.

•

Any community feature that is exclusively related to non-Arm architectures is not supported.

•

Except for Armv6-M, compilation for targets that implement architectures lower than Armv7 is

not supported.

•

The long double data type is not supported for AArch64 state because of limitations in the

current Arm C library.

•

C complex arithmetic is not supported, because of limitations in the current Arm C library.

•

Complex numbers are deﬁned in C++ as a template, std::complex. Arm Compiler for

Embedded supports std::complex with the float and double types, but not the long double

type because of limitations in the current Arm C library.

Non-Conﬁdential

Page 18 of 146

Arm

Compiler for Embedded Migration and Compatibility

Guide

Document ID: 100068_6.20_00_en

Version 6.20

Conﬁguration and Support Information

For C code that uses complex numbers, it is not suﬃcient to recompile with

the C++ compiler to make that code work. How you can use complex numbers

depends on whether or not you are building for Armv8-M architecture-based

processors.

•

You must take care when mixing translation units that are compiled with and without the

[COMMUNITY] -fsigned-char option, and that share interfaces or data structures.

The Arm ABI deﬁnes char as an unsigned byte, and this is the interpretation

used by the C libraries supplied with the Arm compilation tools.

•

There are limitations with the Control Flow Integrity (CFI) sanitizer implementation, -

fsanitize=cfi, which requires Link-Time Optimization (LTO), -flto. The following are likely to

occur:

◦ When using features such as C++ I/O streams, the linker might report errors for a rejected

local symbol, L6654E, or that a symbol is not preserved by the LTO code generation, L6137E.

◦ The linker might report a diagnostic that a symbol has a size that extends outside of its

containing section, L6783E or L6784E.

Use the linker option --diag_suppress 6783 or --diag_suppress 6784 to suppress the

diagnostic.

Alternatives to C complex numbers not being supported

If you are building for Armv8-M architecture-based processors, consider using the free and open-

source CMSIS-DSP library that includes a data type and library functions for complex number

support in C. For more information about CMSIS-DSP and complex number support see the

following sections of the CMSIS documentation:

•

Complex Math Functions

•

Complex Matrix Multiplication

•

Complex FFT Functions

If you are not building for Armv8-M architecture-based processors, consider modifying the aﬀected

part of your project to use the C++ standard template library type std::complex instead.

2.2 Compiler conﬁguration information

Summarizes the FlexNet versions supported by the Arm compilation tools.

FlexNet versions in the compilation tools

Diﬀerent versions of Arm

Compiler for Embedded support diﬀerent versions of FlexNet.

Non-Conﬁdential

Page 19 of 146

剩余145页未读，继续阅读

a291936324

粉丝: 1
资源: 15

Arm Compiler 6.20 迁移与兼容性指南

jdk20-jdk-migration-guide.pdf

查看kafka-server-start.sh路径

SVN转到github

postcss-px-to-viewport: postcss.plugin was deprecated. migration guide:

migrate -path migration -database "postgresql://root:123456@localhost:5432/simple_bank?sslmode=disable" -verbose up 2023/06/06 12:57:44 error: open .: no such file or directory make: *** [migrateup] Error 1

migrate -path db/migration -database "mysql://root:123456789@tcp(0.0.0.0:3306)/mall_db?query" -verbose up 2023/07/23 11:49:27 error: Error 1049: Unknown database 'mall_db'

Update-Database 命令参数详解

typeorm-ts-node-commonjs migration:generate的完整指令

postcss-px-to-viewport: postcss.plugin was deprecated. Migration guide: https://evilmartians.com/chronicles/postcss-8-plugin-mig

activiti自动建表配置

--migration

java.lang.IllegalStateException: A migration from 1 to 2 was required but not found. Please provide the necessary Migration path via RoomDatabase.Builder.addMigration(Migration ...) or allow for destructive migrations via one of the RoomDatabase.Builder.fallbackToDestructiveMigration* methods.

帮忙生成一百个RPA机器人的使用场景

the 'kotlin-android-extensions' gradle plugin is deprecated. please use this migration guide (https://goo.gle/kotlin-android-extensions-deprecation) to start working with view binding (https://developer.android.com/topic/libraries/view-binding) and the 'kotlin-parcelize' plugin.

欧拉 安装 libdrm2

migrate -path db/migration -database "mysql://root:123456789@tcp(0.0.0.0:3306)/mall_db" -verbose up 2023/07/23 12:04:50 error: Error 1049: Unknown database 'mall_db'

class Migration(migrations.Migration):

最新资源

欧拉安装 libdrm2