code logs -> 2024 -> Mon, 01 Jan 2024< code.20231231.log - code.20240102.log >
--- Log opened Mon Jan 01 00:00:47 2024
02:33 Degi_ [Degi@Nightstar-jcqnll.pool.telefonica.de] has joined #code
02:35 Degi [Degi@Nightstar-ts3a5b.pool.telefonica.de] has quit [Ping timeout: 121 seconds]
02:35 Degi_ is now known as Degi
05:46
<&McMartin>
Ha, welp
05:47
<&McMartin>
I've started doing the research for a project in February and have run into probably having to deal with the concept of memory fences instead of just locks
05:47
<&McMartin>
Built a few test programs, got correct answers out, checked the disasm, discovered that the compiler emitted no instructionis for any of the fence points
05:48
<&McMartin>
I *think* what is happening here is that the guarantees I need for this are provided automatically by x86_64's memory model, and that if I want to see actual code emitted for it, I'll have to work with Aarch64 instead
11:28 McMartin [mcmartin@Nightstar-4fcotg.sndgca.sbcglobal.net] has quit [Ping timeout: 121 seconds]
12:36 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has joined #code
14:49 Vornicus [Vorn@Nightstar-ivektl.res.spectrum.com] has joined #code
14:49 mode/#code [+qo Vornicus Vornicus] by ChanServ
17:51 Vornicus [Vorn@Nightstar-ivektl.res.spectrum.com] has quit [Connection closed]
20:42 McMartin [mcmartin@Nightstar-4fcotg.sndgca.sbcglobal.net] has joined #code
20:42 mode/#code [+ao McMartin McMartin] by ChanServ
22:56 McMartin [mcmartin@Nightstar-4fcotg.sndgca.sbcglobal.net] has quit [[NS] Quit: leaving]
23:55 Emmy [Emmy@Nightstar-qo29c7.fixed.kpn.net] has quit [Ping timeout: 121 seconds]
--- Log closed Tue Jan 02 00:00:48 2024
code logs -> 2024 -> Mon, 01 Jan 2024< code.20231231.log - code.20240102.log >

[ Latest log file ]