英特尔汇编语法与AT& T相比的局限性 [英] Limitations of Intel Assembly Syntax Compared to AT&T

查看:54
本文介绍了英特尔汇编语法与AT& T相比的局限性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

对我来说,英特尔语法更容易阅读.如果我只关注Intel语法来遍历汇编林,我会错过任何事情吗?我有什么理由要切换到AT& T(除了能够读取其他人的AT& T程序集之外)?我的第一个线索是,gdb默认使用AT& T.

To me, Intel syntax is much easier to read. If I go traipsing through assembly forest concentrating only on Intel syntax, will I miss anything? Is there any reason I would want to switch to AT&T (outside of being able to read others' AT&T assembly)? My first clue is that gdb uses AT&T by default.

如果这很重要,我的重点仅放在任何关系汇编上,并且可能需要对Linux/BSD和C语言进行语法处理.

If this matters, my focus is only on any relation assembly and syntax may have to Linux/BSD and the C language.

推荐答案

彼此之间没有任何优势.我同意Intel语法很多更容易阅读.请记住,AFAIK,所有GNU工具都可以选择也使用Intel语法.

There is really no advantage to one over the other. I agree though that Intel syntax is much easier to read. Keep in mind that, AFAIK, all GNU tools have the option to use Intel syntax also.

看起来您可以通过以下方式使GDB使用Intel语法:

It looks like you can make GDB use Intel syntax with this:


set disassembly-flavor intel

GCC可以使用-masm=intel执行Intel语法.

GCC can do Intel syntax with -masm=intel.

这篇关于英特尔汇编语法与AT& T相比的局限性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆