Skip to content
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

Consistent handle of namespaces in Auto-Sync #2461

Open
1 of 5 tasks
Rot127 opened this issue Aug 28, 2024 · 0 comments
Open
1 of 5 tasks

Consistent handle of namespaces in Auto-Sync #2461

Rot127 opened this issue Aug 28, 2024 · 0 comments
Labels
Auto-Sync build & packaging Build system and packaging related

Comments

@Rot127
Copy link
Collaborator

Rot127 commented Aug 28, 2024

Feature

  • New architecture module
  • Support for processor extension
  • Add more instruction details (elaborated below)
  • Binding support for: language
  • Other (elaborated below)

Describe the feature you'd like

One of the most annoying things are, that we have no automated way of translate namespace yet.

Some arch modules have function with the same name. And we have make all of them static, otherwise we get linking issues due to duplicated symbols.

The best way is probably to compile each module separately and link it accordingly, if possible. Currently CMake just adds everything to "capstone".

Or at least the LLVM code should be it's own compilation unit. Auto-Sync modules have the ARCHLinkage.h file. With the printer, decoder and reg_name APIs to the module.
So we can make it a compilation unit.

Or we have to move the declarations to the C files and make all of them static. Which is really annoying to patch. So this is not the way we should go if avoidable.

Additional context
...

@Rot127 Rot127 added build & packaging Build system and packaging related Auto-Sync labels Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Sync build & packaging Build system and packaging related
Projects
None yet
Development

No branches or pull requests

1 participant