arm 交叉编译时 gcc 的 Options
https://sourceware.org/binutils/docs/as/ARM-Options.html
https://gcc.gnu.org/onlinedocs/gcc-4.5.3/gcc/i386-and-x86_002d64-Options.html
9.4.1 Options
-mcpu=processor[+extension...]- This option specifies the target processor. The assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target processor. The following processor names are recognized:
arm1,arm2,arm250,arm3,arm6,arm60,arm600,arm610,arm620,arm7,arm7m,arm7d,arm7dm,arm7di,arm7dmi,arm70,arm700,arm700i,arm710,arm710t,arm720,arm720t,arm740t,arm710c,arm7100,arm7500,arm7500fe,arm7t,arm7tdmi,arm7tdmi-s,arm8,arm810,strongarm,strongarm1,strongarm110,strongarm1100,strongarm1110,arm9,arm920,arm920t,arm922t,arm940t,arm9tdmi,fa526(Faraday FA526 processor),fa626(Faraday FA626 processor),arm9e,arm926e,arm926ej-s,arm946e-r0,arm946e,arm946e-s,arm966e-r0,arm966e,arm966e-s,arm968e-s,arm10t,arm10tdmi,arm10e,arm1020,arm1020t,arm1020e,arm1022e,arm1026ej-s,fa606te(Faraday FA606TE processor),fa616te(Faraday FA616TE processor),fa626te(Faraday FA626TE processor),fmp626(Faraday FMP626 processor),fa726te(Faraday FA726TE processor),arm1136j-s,arm1136jf-s,arm1156t2-s,arm1156t2f-s,arm1176jz-s,arm1176jzf-s,mpcore,mpcorenovfp,cortex-a5,cortex-a7,cortex-a8,cortex-a9,cortex-a15,cortex-r4,cortex-r4f,cortex-r5,cortex-r7,cortex-m4,cortex-m3,cortex-m1,cortex-m0,cortex-m0plus,ep9312(ARM920 with Cirrus Maverick coprocessor),i80200(Intel XScale processor)iwmmxt(Intel(r) XScale processor with Wireless MMX(tm) technology coprocessor) andxscale. The special nameallmay be used to allow the assembler to accept instructions valid for any ARM processor.In addition to the basic instruction set, the assembler can be told to accept various extension mnemonics that extend the processor using the co-processor instruction space. For example,
-mcpu=arm920+maverickis equivalent to specifying-mcpu=ep9312.Multiple extensions may be specified, separated by a
+. The extensions should be specified in ascending alphabetical order.Some extensions may be restricted to particular architectures; this is documented in the list of extensions below.
Extension mnemonics may also be removed from those the assembler accepts. This is done be prepending
noto the option that adds the extension. Extensions that are removed should be listed after all extensions which have been added, again in ascending alphabetical order. For example,-mcpu=ep9312+nomaverickis equivalent to specifying-mcpu=arm920.The following extensions are currently supported:
crypto(Cryptography Extensions for v8-A architecture, impliesfp+simd),fp(Floating Point Extensions for v8-A architecture),idiv(Integer Divide Extensions for v7-A and v7-R architectures),iwmmxt,iwmmxt2,maverick,mp(Multiprocessing Extensions for v7-A and v7-R architectures),os(Operating System for v6M architecture),sec(Security Extensions for v6K and v7-A architectures),simd(Advanced SIMD Extensions for v8-A architecture, impliesfp),virt(Virtualization Extensions for v7-A architecture, impliesidiv), andxscale. -march=architecture[+extension...]- This option specifies the target architecture. The assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target architecture. The following architecture names are recognized:
armv1,armv2,armv2a,armv2s,armv3,armv3m,armv4,armv4xm,armv4t,armv4txm,armv5,armv5t,armv5txm,armv5te,armv5texp,armv6,armv6j,armv6k,armv6z,armv6zk,armv6-m,armv6s-m,armv7,armv7-a,armv7ve,armv7-r,armv7-m,armv7e-m,armv8-a,iwmmxtandxscale. If both-mcpuand-marchare specified, the assembler will use the setting for-mcpu.The architecture option can be extended with the same instruction set extension options as the
-mcpuoption. -mfpu=floating-point-format- This option specifies the floating point format to assemble for. The assembler will issue an error message if an attempt is made to assemble an instruction which will not execute on the target floating point unit. The following format options are recognized:
softfpa,fpe,fpe2,fpe3,fpa,fpa10,fpa11,arm7500fe,softvfp,softvfp+vfp,vfp,vfp10,vfp10-r0,vfp9,vfpxd,vfpv2,vfpv3,vfpv3-fp16,vfpv3-d16,vfpv3-d16-fp16,vfpv3xd,vfpv3xd-d16,vfpv4,vfpv4-d16,fpv4-sp-d16,fp-armv8,arm1020t,arm1020e,arm1136jf-s,maverick,neon,neon-vfpv4,neon-fp-armv8, andcrypto-neon-fp-armv8.In addition to determining which instructions are assembled, this option also affects the way in which the
.doubleassembler directive behaves when assembling little-endian code.The default is dependent on the processor selected. For Architecture 5 or later, the default is to assembler for VFP instructions; for earlier architectures the default is to assemble for FPA instructions.
-mthumb- This option specifies that the assembler should start assembling Thumb instructions; that is, it should behave as though the file starts with a
.code 16directive. -mthumb-interwork- This option specifies that the output generated by the assembler should be marked as supporting interworking.
-mimplicit-it=never-mimplicit-it=always-mimplicit-it=arm-mimplicit-it=thumb- The
-mimplicit-itoption controls the behavior of the assembler when conditional instructions are not enclosed in IT blocks. There are four possible behaviors. Ifneveris specified, such constructs cause a warning in ARM code and an error in Thumb-2 code. Ifalwaysis specified, such constructs are accepted in both ARM and Thumb-2 code, where the IT instruction is added implicitly. Ifarmis specified, such constructs are accepted in ARM code and cause an error in Thumb-2 code. Ifthumbis specified, such constructs cause a warning in ARM code and are accepted in Thumb-2 code. If you omit this option, the behavior is equivalent to-mimplicit-it=arm. -mapcs-26-mapcs-32- These options specify that the output generated by the assembler should be marked as supporting the indicated version of the Arm Procedure. Calling Standard.
-matpcs- This option specifies that the output generated by the assembler should be marked as supporting the Arm/Thumb Procedure Calling Standard. If enabled this option will cause the assembler to create an empty debugging section in the object file called .arm.atpcs. Debuggers can use this to determine the ABI being used by.
-mapcs-float- This indicates the floating point variant of the APCS should be used. In this variant floating point arguments are passed in FP registers rather than integer registers.
-mapcs-reentrant- This indicates that the reentrant variant of the APCS should be used. This variant supports position independent code.
-mfloat-abi=abi- This option specifies that the output generated by the assembler should be marked as using specified floating point ABI. The following values are recognized:
soft,softfpandhard. -meabi=ver- This option specifies which EABI version the produced object files should conform to. The following values are recognized:
gnu,4and5. -EB- This option specifies that the output generated by the assembler should be marked as being encoded for a big-endian processor.
-EL- This option specifies that the output generated by the assembler should be marked as being encoded for a little-endian processor.
-k- This option specifies that the output of the assembler should be marked as position-independent code (PIC).
--fix-v4bx- Allow
BXinstructions in ARMv4 code. This is intended for use with the linker option of the same name. -mwarn-deprecated-mno-warn-deprecated- Enable or disable warnings about using deprecated options or features. The default is to warn.
-mccs- Turns on CodeComposer Studio assembly syntax compatibility mode.
arm 交叉编译时 gcc 的 Options的更多相关文章
- 建立ARM交叉编译环境 (arm-none-linux-gnueabi-gcc with EABI)【转】
转自:http://lib.csdn.net/article/embeddeddevelopment/60172?knId=886 建立ARM交叉编译环境 (arm-none-linux-gnueab ...
- Linux ARM交叉编译工具链制作过程【转】
本文转载自:http://www.cnblogs.com/Charles-Zhang-Blog/archive/2013/02/21/2920999.html 一.下载源文件 源代码文件及其版本与下载 ...
- Ubuntu18.04 LTS x64 构建ARM交叉编译环境(尝试,但失败了!!!估计是编译器没选对)
[测试而已,由于需要了解编译器和处理器体系,因此先放弃该方法] 动机 入门嵌入式开发,又需要 Windows 又需要 Linux,但资料给的竟然是 Ubuntu9,导致我不能使用 VSCode Rem ...
- Ubuntu12.04下arm交叉编译环境的建立
http://blog.csdn.net/heyangya2009/article/details/5424376 备注:ubuntu12.04+Android+Real6410 在主机上用来编译其他 ...
- 【转】ARM交叉编译工具链
原文网址:http://www.veryarm.com/cross-tools 为什么要用交叉编译器? 交叉编译通俗地讲就是在一种平台上编译出能运行在体系结构不同的另一种平台上的程序,比如在PC平台( ...
- Linux学习笔记——怎样在交叉编译时使用共享库
0.前言 在较为复杂的项目中会利用到交叉编译得到的共享库(*.so文件).在这样的情况下便会产生下面疑问,比如: [1]交叉编译时的共享库是否须要放置于目标板中,假设须要放置在哪个文件 ...
- ARM交叉编译工具链分类说明
转载整理自:http://www.veryarm.com/cross-tools 从授权上,ARM交叉编译工具链分为免费授权版和付费授权版. 免费版目前有三大主流工具商提供,第一是GNU(提供源码,自 ...
- ARM交叉编译工具链
交叉编译工具链是一个由编译器.连接器和解释器组成的综合开发环境,交叉编译工具链主要由binutils.gcc和glibc三个部分组成. 免费版目前有三大主流工具商提供,第一是GNU(提供源码,自行编译 ...
- arm交叉编译 扫盲贴
ARM交叉编译工具链 为什么要用交叉编译器? 交叉编译通俗地讲就是在一种平台上编译出能运行在体系结构不同的另一种平台上的程序, 比如在PC平台(X86 CPU)上编译出能运行在以ARM为内核的CPU平 ...
随机推荐
- HttpContext
HttpContext 类:封装有关个别 HTTP 请求的所有 HTTP 特定的信息.也有人叫上下文信息. 1.生存周期:从客户端用户点击并产生了一个向服务器发送请求开始---服务器处理完请求并生成返 ...
- 一步步学习NHibernate(4)——多对一,一对多,懒加载(1)
请注明转载地址:http://www.cnblogs.com/arhat 通过上一章的学习,我们学会如何使用NHibernate对数据的简单查询,删除,更新和插入,那么如果说仅仅是这样的话,那么NHi ...
- 用android-x86模拟器不能运行程序错误Tag:libc的问题
如果用的是x86的android模拟器,运行软件时一闪就关闭logcat中:类似:Fatal signal 11 (SIGSEGV) at 0x00000078 (code=1), thread 16 ...
- swift版本hello
import UIKit class ViewController: UIViewController { @IBOutlet var button : UIButton? //var alertVi ...
- word-wrap同word-break的区别(转)
本文列举了兼容 IE 和 FF 的换行 CSS 推荐样式,详细介绍了word-wrap同word-break的区别. 兼容 IE 和 FF 的换行 CSS 推荐样式 最好的方式是 word-wrap: ...
- 切换加上延迟加载js代码
切换加上延迟加载js代码 (function(){ var tit = $("#tab02 li"), con = $("#wrapmp>div"), c ...
- portal、portlet、portlet容器三个概念
什么是portal Portlet规范中是这样定义portal的: A portal is a web based application that –commonly- provides perso ...
- RadioGroup 的 RadioButton 选择改变字体颜色和背景颜色
RadioGroup <RadioGroup android:id="@+id/client_charge_radiogroup" android:layout_width= ...
- apt-get用法
转自apt-get语法- - 对于debian来说,安装软件大多都是通过apt-get来实现的. 1.apt-get update 更新软件包信息库.在Debian中,软件包是通过一个数据库来管理的, ...
- ASP.net Application及Session 的start end 方法总结
经过几天的摸索,试验,今天终于可以将Application及Session对象的Start和End方法做下总结了. Application_start: 第一个访问网站的用户会触发该方法. 通常会在该 ...