bindgen can't generate thread local variables correctly

[framlog]

I don't know whether it's really an issue since stable rust doesn't support thread_local yet.

Input C/C++ Header

static __thread int variable_1 = 0;
thread_local int variable_2 = 0;

Bindgen Invocation

bindgen::Builder::default()
    .header("input.h")
    .rust_target(bindgen::RustTarget::Nightly)
    .generate()
    .unwrap()

or

$ bindgen input.h --whatever --flags

Actual Results

pub static mut variable_1 ...

Expected Results

#[thread_local]
pub static mut variable_1

[emilio]

There's another issue, I think, which is that thread-local vars don't have symbols, so I'm not sure it's possible to touch a C thread-local variable without going through FFI.

There's definitely a bug in there, if I'm right we shouldn't be generating TLS vars at all anyway.

[fintelia]

I'm also impacted by this issue. Is it possible to work around by blacklisting and providing the correct Rust incantation myself, or will there still be problems at the link stage?

[emilio]

Yes, you should be able to just whitelist it, but I don't think you can provide the rust definition, given I don't think there's a standard way to create TLS vars across languages