-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add LoongArch Support #1
base: la64/master
Are you sure you want to change the base?
Conversation
修改前输出:
修改后输出:
|
这是直接把 32位干掉了吗?现在用的这个名字,看起来就是不会再给32位任何机会了啊 |
根据新的binutils 来写的 |
return false; | ||
} | ||
|
||
return (processor_flag() & static_cast<uint32_t>(f)) > 0; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这边看看能不能有机会正确处理 EF_LOONGARCH_OBJABI_V1
:如果 f
是这玩意,则 mask 出位域做相等比较,否则像现在写法一样做 bitwise and 比较。
工程实践上,操作这个 flag 完全是合理需求,所以如果你要适配这个库,一定要支持它。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这边看看能不能有机会正确处理 EF_LOONGARCH_OBJABI_V1:如果 f 是这玩意,则 mask 出位域做相等比较,否则像现在写法一样做 bitwise and 比较。
手头紧急工作告一段落,接着搞LIEF。 我咨询了一下相关的同事,上游支持的代码都是新世界的,不考虑旧世界,上游默认都是V1
现在用 ELFCLASS32/ELFCLASS64 区分 32 位和 64 位。 |
这样说就靠谱多了,名字也比原来看着舒服些。 |
增加LA的支持,please review,thanks! @loongarch64/dev-team