Multi-Threading in C — Barriers

The sloppy cut at 29:47 was due to me accidentally leaking my IP. Sorry for it being so sloppy, I had to do it with ffmpeg.

References:

Support:

Feel free to use this video to make highlights and upload them to YouTube (also please put the link to this channel in the description)

[javali]

dude... you dont know nothing what you doing. you dont create threads in a "game loop". use a thread pool... that simple. so the starting time and overhead of threads dont matter. learn first before streaming and shaming urself.

[rogo]

'__restrict' (or just 'restrict' in C) is not an indicator that pointer isn't nullable. It's about that this pointer is ONLY pointer, that can point to this variable. It is very cool way to promise to the compiler that we won't do this thing, and because of that it will make some optimizations (for example, if you don't provide 'restrict', compiler will copy-paste value from pointed address every time you use value of the pointer).

[diegorocha]

The time has come to rewrite it in GO!

[rogo]

Destroying barrier after the whole Renderer was nulled to the hell :D

[berndeckenfels]

21:30 Synchronisation is not the issue but you might get a different clock in other thread, so it’s tricky to measure that (your cpu might be old enough to not take advantage of it?)

[beyondcatastrophe_]

50:00 you're clearing the barrier before destroying it...