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

Avoid \u{1} prefix when the user overrode item names #3175

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

bjorn3
Copy link
Member

@bjorn3 bjorn3 commented Mar 20, 2025

\u{1} is an LLVM specific extension which other rustc codegen backends do not support.

Fixes #2935

@bjorn3 bjorn3 changed the title Avoid \u{1} prefix when the user overrode symbol names Avoid \u{1} prefix when the user overrode item names Mar 20, 2025
\u{1} is an LLVM specific extension which other rustc codegen backends
do not support.
@bjorn3 bjorn3 force-pushed the better_link_name_handling branch from fc322e0 to 50eb27f Compare March 20, 2025 15:16
@bjorn3
Copy link
Member Author

bjorn3 commented Mar 20, 2025

Why does the Publish on crates.io workflow get invoked even though this PR hasn't been merged? It gives me a failure notification. https://github.com/rust-lang/rust-bindgen/actions/runs/13972867609

@bjorn3
Copy link
Member Author

bjorn3 commented Mar 20, 2025

Right, for Mach-O all symbols get mangled to add an _ prefix. Is there a way in libclang to get the symbol name before the object file format specific mangling but after C++ mangling? (aka the input LLVM expects then not using \u{1})

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

Successfully merging this pull request may close these issues.

Avoid using \u{1} prefixes in symbol names where possible
1 participant