bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

2022-11-07 Thread Rob Browning
Rob Browning writes: > OK, so unfortunately I don't actually recall how I came up with that > number, but I can start over with some canonical approach to compute the > value if we like. I hacked up hash.c to let me call wide_string_hash() directly and printed the hash for wchar_t {0x3A0,

bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation

2022-11-07 Thread Maxim Cournoyer
Hi, Maxim Cournoyer writes: [...] > I've tested both 3.0.8 from Guix on multiple machines (including Berlin) > and 2.2 from Debian 10, and ran the above snippet; it grows initially > but stabilize quickly and then doesn't budge. I've let it run for more > than an hour. Actually, it does

bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation

2022-11-07 Thread Maxim Cournoyer
Hi Ludovic, Ludovic Courtès writes: > (This is a followup to , > itself a followup to .) > > Consider this code: > > ;; https://issues.guix.gnu.org/58631 > ;; https://github.com/wingo/fibers/issues/65 > > (define loss

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

2022-11-07 Thread Ludovic Courtès
Rob Browning skribis: > So this change *could* alter results, but only for non-ASCII strings, > and those results would have been wrong (i.e. relying on uninitialized > memory). OK, that was my understanding too. > That leaves the size_t -> long change in scm_i_str2symbol(), and I don't >

bug#56413: [PATCH 1/1] scm_i_utf8_string_hash: compute u8 chars not bytes

2022-11-07 Thread Ludovic Courtès
Rob Browning skribis: >> Is this a documented example of Jenkins? Or did you use a reference >> implementation? > > Jenkins? That’s the name of the hash function in question. If not, where did you get that example from? :-) Thanks, Ludo’.