8000 Emulation options should be consistent with each other · Issue #58 · qualcomm/eld · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Emulation options should be consistent with each other #58

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

Open
partaror opened this issue Apr 23, 2025 · 2 comments
Open

Emulation options should be consistent with each other #58

partaror opened this issue Apr 23, 2025 · 2 comments

Comments

@partaror
Copy link

Currently, we do not do consistency checks for the passed emulation options. For example, -m <emulation> option simply overrides the other emulation options such as -mcpu <cpu> and -march <arch>. We should error-out if emulation options are inconsistent with each other, for example: ld.eld -o a.out /dev/null -m v68 -mcpu hexagonv99.

@quic-seaswara
Copy link
Contributor
quic-seaswara commented Apr 23, 2025

what does clang do in this case ?

I feel that this logic if exists in LLVM can be borrowed to all the tools that use -mcpu/-march/-mtriple/emulation

We want to make sure at all times be consistent with clang.

If you want to pursue this, it has to be discussed with the LLVM community.

@partaror
Copy link
Author

what does clang do in this case ?

Clang does error out when we mix riscv/arm/aarch target with incorrect -mcpu. However, it does not error out when mixing different hexagon cpu versions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0