#threadsafe — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #threadsafe, aggregated by home.social.
-
Parallel builds in CI/CD are nice and dandy, but one has to remember that having a couple dozen simultaneous jobs update the same file at the same time can lead to undesirable side effects.
-
Parallel builds in CI/CD are nice and dandy, but one has to remember that having a couple dozen simultaneous jobs update the same file at the same time can lead to undesirable side effects.
-
getenv() + putenv() + setenv() 的 thread-safe 問題
在「Improving Steam Client Stability on Linux (ttimo.typepad.com)」這邊看到的，原文在「Improving Steam Client stability on Linux: setenv and multit
#Computer #Linux #Murmuring #OS #Programming #Security #Software #env #getenv #glibc #linux #memory #multihtreading #putenv #safe #safety #setenv #thread #threadsafe #threading #threads
-
getenv() + putenv() + setenv() 的 thread-safe 問題
在「Improving Steam Client Stability on Linux (ttimo.typepad.com)」這邊看到的，原文在「Improving Steam Client stability on Linux: setenv and multit
#Computer #Linux #Murmuring #OS #Programming #Security #Software #env #getenv #glibc #linux #memory #multihtreading #putenv #safe #safety #setenv #thread #threadsafe #threading #threads
-
getenv() + putenv() + setenv() 的 thread-safe 問題
在「Improving Steam Client Stability on Linux (ttimo.typepad.com)」這邊看到的，原文在「Improving Steam Client stability on Linux: setenv and multit
#Computer #Linux #Murmuring #OS #Programming #Security #Software #env #getenv #glibc #linux #memory #multihtreading #putenv #safe #safety #setenv #thread #threadsafe #threading #threads
-
getenv() + putenv() + setenv() 的 thread-safe 問題
在「Improving Steam Client Stability on Linux (ttimo.typepad.com)」這邊看到的，原文在「Improving Steam Client stability on Linux: setenv and multit
#Computer #Linux #Murmuring #OS #Programming #Security #Software #env #getenv #glibc #linux #memory #multihtreading #putenv #safe #safety #setenv #thread #threadsafe #threading #threads
-
getenv() + putenv() + setenv() 的 thread-safe 問題
在「Improving Steam Client Stability on Linux (ttimo.typepad.com)」這邊看到的，原文在「Improving Steam Client stability on Linux: setenv and multit
#Computer #Linux #Murmuring #OS #Programming #Security #Software #env #getenv #glibc #linux #memory #multihtreading #putenv #safe #safety #setenv #thread #threadsafe #threading #threads
-
Just realised that the code I wrote which contains a #BufferOverflow if you compile it for a 256 bit CPU is also not #ThreadSafe. Truly I am an awful person.
-
Just realised that the code I wrote which contains a #BufferOverflow if you compile it for a 256 bit CPU is also not #ThreadSafe. Truly I am an awful person.
-
Just realised that the code I wrote which contains a #BufferOverflow if you compile it for a 256 bit CPU is also not #ThreadSafe. Truly I am an awful person.
-
Just realised that the code I wrote which contains a #BufferOverflow if you compile it for a 256 bit CPU is also not #ThreadSafe. Truly I am an awful person.
-
And what happened? After I had it all working, and I wanted to say, OK, let's use multitasking to share out all the work amongst the available CPU cores?
Remember, I'd put zero thought into trying to make the code #ThreadSafe, I was just writing single-threaded game play, but I *was* using #immutable vals instead of mutable vars.
12/
-
And what happened? After I had it all working, and I wanted to say, OK, let's share out all the work amongst the available CPU cores?
Remember, I'd put zero thought into trying to make the code #ThreadSafe, I was just writing single-threaded game play.
-
And what happened? After I had it all working, and I wanted to say, OK, let's use multitasking to share out all the work amongst the available CPU cores?
Remember, I'd put zero thought into trying to make the code #ThreadSafe, I was just writing single-threaded game play, but I *was* using #immutable vals instead of mutable vars.
12/
-
And what happened? After I had it all working, and I wanted to say, OK, let's share out all the work amongst the available CPU cores?
Remember, I'd put zero thought into trying to make the code #ThreadSafe, I was just writing single-threaded game play, but I *was* using #immutable vals instead of mutable vars.
12/
-
And what happened? After I had it all working, and I wanted to say, OK, let's use multitasking to share out all the work amongst the available CPU cores?
Remember, I'd put zero thought into trying to make the code #ThreadSafe, I was just writing single-threaded game play, but I *was* using #immutable vals instead of mutable vars.
12/