2025/05/12

Newest at the top

2025-05-12 14:37:11 +0200jespada(~jespada@r179-24-29-12.dialup.adsl.anteldata.net.uy) (Quit: Textual IRC Client: www.textualapp.com)
2025-05-12 14:35:18 +0200xff0x(~xff0x@2405:6580:b080:900:7188:fe4c:4162:a20)
2025-05-12 14:35:07 +0200ljdarj(~Thunderbi@user/ljdarj) ljdarj
2025-05-12 14:30:05 +0200xff0x(~xff0x@ai099192.d.east.v6connect.net) (Quit: xff0x)
2025-05-12 14:26:20 +0200ttybitnik(~ttybitnik@user/wolper) ttybitnik
2025-05-12 14:21:06 +0200jespada(~jespada@r179-24-29-12.dialup.adsl.anteldata.net.uy) jespada
2025-05-12 14:11:44 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 265 seconds)
2025-05-12 14:09:37 +0200j1n37(~j1n37@user/j1n37) (Ping timeout: 276 seconds)
2025-05-12 14:08:48 +0200comerijn(~merijn@77.242.116.146) merijn
2025-05-12 14:08:09 +0200j1n37-(~j1n37@user/j1n37) j1n37
2025-05-12 13:52:18 +0200lortabac(~lortabac@2a01:e0a:541:b8f0:55ab:e185:7f81:54a4)
2025-05-12 13:40:34 +0200td_(~td@i53870921.versanet.de)
2025-05-12 13:28:59 +0200td_(~td@i53870921.versanet.de) (Quit: waking up from the american dream ...)
2025-05-12 13:28:47 +0200chexum(~quassel@gateway/tor-sasl/chexum) chexum
2025-05-12 13:28:27 +0200chexum_(~quassel@gateway/tor-sasl/chexum) (Remote host closed the connection)
2025-05-12 13:21:22 +0200JeremyB99(~JeremyB99@172.87.18.1)
2025-05-12 13:20:49 +0200xff0x(~xff0x@ai099192.d.east.v6connect.net)
2025-05-12 13:18:14 +0200JeremyB99(~JeremyB99@172.87.18.1) (Ping timeout: 260 seconds)
2025-05-12 13:03:36 +0200JeremyB99(~JeremyB99@172.87.18.1)
2025-05-12 12:54:18 +0200vgtw(~vgtw@user/vgtw) (Ping timeout: 276 seconds)
2025-05-12 12:53:21 +0200vgtw_(~vgtw@user/vgtw) vgtw
2025-05-12 12:51:46 +0200JeremyB99(~JeremyB99@172.87.18.1) (Read error: Connection reset by peer)
2025-05-12 12:39:07 +0200merijn(~merijn@77.242.116.146) merijn
2025-05-12 12:36:04 +0200euleritian(~euleritia@dynamic-176-006-133-103.176.6.pool.telefonica.de)
2025-05-12 12:35:24 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 245 seconds)
2025-05-12 12:34:06 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 265 seconds)
2025-05-12 12:30:13 +0200xff0x(~xff0x@fsb6a9491c.tkyc517.ap.nuro.jp) (Ping timeout: 244 seconds)
2025-05-12 12:29:32 +0200merijn(~merijn@77.242.116.146) merijn
2025-05-12 12:28:57 +0200wootehfoot(~wootehfoo@user/wootehfoot) wootehfoot
2025-05-12 12:28:13 +0200tromp(~textual@2001:1c00:3487:1b00:ecd3:a00f:e9d8:9bf6) (Ping timeout: 276 seconds)
2025-05-12 12:23:00 +0200Frostillicus(~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net) (Ping timeout: 260 seconds)
2025-05-12 12:17:05 +0200comerijn(~merijn@77.242.116.146) (Ping timeout: 244 seconds)
2025-05-12 12:16:02 +0200Frostillicus(~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net)
2025-05-12 12:15:48 +0200 <tomsmeding> only computational complexity has a chance of being hardware-independent, though I wouldn't be surprised if you can come up with edge cases where a compiler is able to e.g. optimise a loop away to a constant operation on one architecture but not on another
2025-05-12 12:14:48 +0200 <tomsmeding> modern CPUs have counters for this
2025-05-12 12:14:38 +0200 <tomsmeding> somewhat related, though: if you accept hardware-bound results, you can strongly reduce noise effects by not measuring time but number of instructions executed
2025-05-12 12:14:03 +0200 <tomsmeding> there is no such thing as hardware-independent performance
2025-05-12 12:13:58 +0200 <tomsmeding> __monty__: the optimisations that a compiler does to your code are instruction-set architecture dependent
2025-05-12 12:12:29 +0200 <Hecate> __monty__: there's not "nothing", but there's few things. Useful things are still bound to the laws of physics
2025-05-12 12:11:15 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr)
2025-05-12 12:07:48 +0200sabathan2(~sabathan@amarseille-159-1-12-107.w86-203.abo.wanadoo.fr) (Read error: Connection reset by peer)
2025-05-12 12:02:27 +0200 <__monty__> This is more of an inquiry for theoretical results. I find it hard to believe that there's *nothing* you can measure independently from a specific hardware configuration.
2025-05-12 12:01:27 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de)
2025-05-12 12:01:04 +0200 <__monty__> No, that's not actually what I want.
2025-05-12 12:00:56 +0200merijn(~merijn@77.242.116.146) (Ping timeout: 252 seconds)
2025-05-12 12:00:49 +0200euleritian(~euleritia@ip4d17f864.dynamic.kabel-deutschland.de) (Ping timeout: 248 seconds)
2025-05-12 11:59:14 +0200tromp(~textual@2001:1c00:3487:1b00:ecd3:a00f:e9d8:9bf6)
2025-05-12 11:59:09 +0200Frostillicus(~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net) (Ping timeout: 245 seconds)
2025-05-12 11:58:25 +0200comerijn(~merijn@77.242.116.146) merijn
2025-05-12 11:54:41 +0200Frostillicus(~Frostilli@pool-71-174-119-56.bstnma.fios.verizon.net)