Skip to contentSkip to conversation

Is gcc thread-unsafe?

DISCUSSION [email protected] 1 participant 1 message Oct 28, 2007

lore
Share & tools
lore
#0 lore raw

Just a note on the attribute((acquire,release)) proposal:

It's nice to be able to annotate functions, but please don't forget to provide a way to write such functions. Ultimately, there will be an asm() or assignment that is the acquire or release point, and GCC needs to know that so it can compile the function itself (possibly inline).

Having just a function attribute leaves the problem that

void __attribute__((noreturn))
_exit(int status)

{
	asm("int 0x80" : : (__NR_exit) "a", (status) "b" );
}

generates a complaint about a noreturn function returning, because there's no way to tell GCC about a non-returning statement.