2026-04-01 11:06:23 -06:00
..
2025-12-19 17:34:35 -08:00
first pass at (rdi -> loose rdim) path, used in (rdi * ... * rdi) -> rdi joining in radbin; plug in regular conversion path before voff -> line & breakpad paths in radbin, such that PDBs, DWARFs, RDIs, etc. can be used as input; fix up voff -> line path to plug into regular output systems; remove String8 union thing - three reasons: (a) it was only ever introduced for convenience in Linux layers, so let's just keep zero-terminated Linux nonsense in Linux land, (b) it was just alternate syntax for a cast, so let's just cast, (c) it was misleading - 'cstr' implies null-termination, which String8 of course doesn't guarantee. this led to some misuses, where .cstr was trusted to be zero-terminated, when that was not necessarily true (semaphore opening).
2026-03-03 16:24:54 -08:00
2026-03-09 14:36:05 -07:00
2026-02-11 15:27:05 -08:00
2025-10-16 15:57:43 -07:00
2025-10-07 16:24:54 -07:00
2026-04-01 11:06:23 -06:00
2026-02-20 22:08:26 -08:00
2026-03-04 11:49:04 -08:00
first pass at (rdi -> loose rdim) path, used in (rdi * ... * rdi) -> rdi joining in radbin; plug in regular conversion path before voff -> line & breakpad paths in radbin, such that PDBs, DWARFs, RDIs, etc. can be used as input; fix up voff -> line path to plug into regular output systems; remove String8 union thing - three reasons: (a) it was only ever introduced for convenience in Linux layers, so let's just keep zero-terminated Linux nonsense in Linux land, (b) it was just alternate syntax for a cast, so let's just cast, (c) it was misleading - 'cstr' implies null-termination, which String8 of course doesn't guarantee. this led to some misuses, where .cstr was trusted to be zero-terminated, when that was not necessarily true (semaphore opening).
2026-03-03 16:24:54 -08:00
2025-10-09 11:24:48 -07:00
2025-11-07 12:00:40 -08:00
2026-02-27 11:07:19 -08:00
2025-12-28 01:16:55 -08:00
2026-03-04 11:49:04 -08:00
2025-10-23 12:10:23 -07:00
2025-10-09 11:24:48 -07:00
2025-09-19 16:55:07 -07:00
2026-02-13 20:59:26 -08:00
2026-01-12 19:06:29 -08:00
2026-03-04 11:49:04 -08:00
2026-03-10 16:01:33 -07:00
2026-03-09 15:15:48 -07:00
2026-03-04 11:41:51 -08:00
2025-06-02 14:13:57 -07:00
2026-02-18 16:16:48 -08:00
first pass at (rdi -> loose rdim) path, used in (rdi * ... * rdi) -> rdi joining in radbin; plug in regular conversion path before voff -> line & breakpad paths in radbin, such that PDBs, DWARFs, RDIs, etc. can be used as input; fix up voff -> line path to plug into regular output systems; remove String8 union thing - three reasons: (a) it was only ever introduced for convenience in Linux layers, so let's just keep zero-terminated Linux nonsense in Linux land, (b) it was just alternate syntax for a cast, so let's just cast, (c) it was misleading - 'cstr' implies null-termination, which String8 of course doesn't guarantee. this led to some misuses, where .cstr was trusted to be zero-terminated, when that was not necessarily true (semaphore opening).
2026-03-03 16:24:54 -08:00
2025-09-05 15:19:30 -07:00
2026-03-17 23:19:57 -07:00
2025-09-23 10:58:17 -07:00
2026-03-04 11:28:53 -08:00
2026-02-10 23:57:43 -08:00
2026-03-18 21:20:56 -07:00
2026-02-13 20:59:26 -08:00
2026-02-11 17:20:38 -08:00
first pass at (rdi -> loose rdim) path, used in (rdi * ... * rdi) -> rdi joining in radbin; plug in regular conversion path before voff -> line & breakpad paths in radbin, such that PDBs, DWARFs, RDIs, etc. can be used as input; fix up voff -> line path to plug into regular output systems; remove String8 union thing - three reasons: (a) it was only ever introduced for convenience in Linux layers, so let's just keep zero-terminated Linux nonsense in Linux land, (b) it was just alternate syntax for a cast, so let's just cast, (c) it was misleading - 'cstr' implies null-termination, which String8 of course doesn't guarantee. this led to some misuses, where .cstr was trusted to be zero-terminated, when that was not necessarily true (semaphore opening).
2026-03-03 16:24:54 -08:00
2026-03-29 12:07:27 -07:00
2026-02-17 03:04:14 -08:00
2026-03-10 16:01:33 -07:00
2025-12-05 16:39:02 -08:00
2026-02-27 11:07:19 -08:00
2025-11-13 10:53:29 -08:00
2026-03-09 15:15:48 -07:00
2026-03-09 14:36:05 -07:00
2025-12-18 20:06:20 -08:00
2025-11-07 14:47:14 -08:00
2026-02-17 03:04:14 -08:00
2026-01-22 13:30:03 -08:00
2025-09-05 15:19:31 -07:00
2025-10-07 16:24:54 -07:00
2025-11-07 10:33:17 -08:00
2026-03-04 11:28:53 -08:00
2026-03-17 14:44:07 -07:00
2025-11-07 13:40:24 -08:00
2026-03-02 12:17:03 -08:00