When using TLS from the global allocator on arm64 macos, I get the following fatal run

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

runtime error: global allocator may not use TLS on arm64 macos about rust HOT 6 CLOSED

MarinPostma commented on July 19, 2024

runtime error: global allocator may not use TLS on arm64 macos

from rust.

Comments (6)

workingjubilee commented on July 19, 2024 1

doesn't seem to be anything to fix here, currently?

from rust.

joboet commented on July 19, 2024

The message describes the problem: the global allocator must not use thread_local!, as the implementation of the macro needs to allocate on most platforms.

We may in the future decide to allow this by using the system allocator here, but this is fundamentally just the tip of the iceberg: nearly every API in std may allocate – I'd argue that you should not use std at all when implementing your own global allocator.

from rust.

workingjubilee commented on July 19, 2024

Grepping the rust repo returns nothing for that error either,

@MarinPostma You are searching overly specifically. The first part, "fatal runtime error", is an error from rtabort!:

rust/library/std/src/rt.rs

Lines 39 to 42 in a299aa5

 macro_rules! rtabort { 

 ($($t:tt)*) => { 

 { 

 rtprintpanic!("fatal runtime error: {}\n", format_args!($($t)*));

The second part is inside the TLS dtor registration, currently:

rust/library/std/src/sys/thread_local/destructors/list.rs

Lines 4 to 13 in a299aa5

 #[thread_local] 

 static DTORS: RefCell<Vec<(*mut u8, unsafe extern "C" fn(*mut u8))>> = RefCell::new(Vec::new()); 

 pub unsafe fn register(t: *mut u8, dtor: unsafe extern "C" fn(*mut u8)) { 

 let Ok(mut dtors) = DTORS.try_borrow_mut() else { 

 // This point can only be reached if the global allocator calls this 

 // function again. 

 // FIXME: maybe use the system allocator instead? 

 rtabort!("the global allocator may not use TLS with destructors"); 

 };

from rust.

MarinPostma commented on July 19, 2024

@workingjubilee that's not the one, notice the absence of "in destructor"

from rust.

ChrisDenton commented on July 19, 2024

Yes, the error message has been tweaked since then but it's still the same error condition. Here's where it is on the 1.79 branch

rust/library/std/src/sys/pal/unix/thread_local_dtor.rs

Lines 105 to 109 in 129f3b9

 match DTORS.try_borrow_mut() { 

 Ok(mut dtors) => dtors.push((t, dtor)), 

 Err(_) => rtabort!("global allocator may not use TLS"), 

 }

from rust.

workingjubilee commented on July 19, 2024

there are actually 5 copies of it on the 1.79 branch.

which is why the refactoring that made there be only one.

from rust.

Recommend Projects

runtime error: global allocator may not use TLS on arm64 macos about rust HOT 6 CLOSED

Comments (6)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	macro_rules! rtabort {
	($($t:tt)*) => {
	{
	rtprintpanic!("fatal runtime error: {}\n", format_args!($($t)*));

	#[thread_local]
	static DTORS: RefCell<Vec<(mut u8, unsafe extern "C" fn(mut u8))>> = RefCell::new(Vec::new());

	pub unsafe fn register(t: mut u8, dtor: unsafe extern "C" fn(mut u8)) {
	let Ok(mut dtors) = DTORS.try_borrow_mut() else {
	// This point can only be reached if the global allocator calls this
	// function again.
	// FIXME: maybe use the system allocator instead?
	rtabort!("the global allocator may not use TLS with destructors");
	};

	match DTORS.try_borrow_mut() {
	Ok(mut dtors) => dtors.push((t, dtor)),
	Err(_) => rtabort!("global allocator may not use TLS"),
	}