| 26 Oct 2024 |
 gluonix | as you may know, nix has a steep learning curve, hence most dev teams prefer docker, unless they have no choice 😆 | 01:03:01 |
| 29 Oct 2024 |
|  jzbor changed their profile picture. | 17:10:18 |
|  eva removed their profile picture. | 22:26:39 |
| eva set a profile picture. | 22:26:54 |
| 30 Oct 2024 |
|  @seapat:matrix.org left the room. | 07:49:55 |
| 2 Nov 2024 |
|  Mel joined the room. | 03:07:18 |
|  Artem Markov changed their display name from Artem Markov to drownbes. | 08:42:16 |
| 5 Nov 2024 |
|  @grossmap:in.tum.de left the room. | 14:15:59 |
| 6 Nov 2024 |
|  @peddie:matrix.org left the room. | 12:33:19 |
| 8 Nov 2024 |
|  @printfn:matrix.org left the room. | 06:13:24 |
 p14 | I know there was some interest in having a PGO/LTO/BOLT clang build, as well. Some notes on build reproduciblity when PGO is involved: https://discourse.llvm.org/t/pgo-profile-reproducibility/82861/6
TL;DR: For profiles it is not enough for the profiling mechanism to be deterministic and the workload to have a deterministic output; the workload must compute the output in a flow-control deterministic way. Clang unfortunately uses inodes in a hash map, which makes the profile not reproducible, so it's not currently possible to have a reproducible PGO clang build. (Unless you control the inode integers that clang sees during profiling, among other horrible details). | 11:41:38 |
| 12 Nov 2024 |
|  pfhuh joined the room. | 05:55:01 |
| 13 Nov 2024 |
|  Inayet joined the room. | 22:16:32 |
