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

ir: Don't crash with built-in unexposed types from libclang. #2339

Merged
merged 1 commit into from
Nov 9, 2022

Conversation

emilio
Copy link
Contributor

@emilio emilio commented Nov 9, 2022

This fixes #2325.

The issue is that __bf16 is not exposed at all by libclang, which causes us to crash. It's a bit of a shame libclang doesn't expose it but there's no rust equivalent I think, so this should be ok for now.

Unfortunately no test because the header crashes older clang versions.

This fixes rust-lang#2325.

The issue is that `__bf16` is not exposed at all by libclang, which
causes us to crash. It's a bit of a shame libclang doesn't expose it but
there's no rust equivalent I think, so this should be ok for now.

Unfortunately no test because the header crashes older clang versions.
@emilio emilio merged commit c03b376 into rust-lang:master Nov 9, 2022
@emilio emilio deleted the bf16 branch November 9, 2022 12:54
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.

thread 'main' panicked at 'Not able to resolve vector element?: Continue', bindgen/ir/ty.rs:1149:22
1 participant