{"push_id":4302213835,"size":2,"distinct_size":2,"ref":"refs/heads/master","head":"f3bbda1d210925aae699ff84eaa7eb03f8f43c11","before":"3a185971d49c8835637e520427888ea79d075f3f","commits":[{"sha":"975139983456142f5489071a2c7db2b28453aeff","author":{"name":"Thomas Gazagnaire","email":"5f50a84c1fa3bcff146405017f36aec1a10a9e38@gazagnaire.org"},"message":"Do not allocate 64k bytes buffers on the thread stack\n\nTo avoid allocating on the stack, keep the runtime lock so that OCaml objects\nare not moved around.\n\nThis is needed because thread stack are very small on musl<1.1.21 (80k).\n\nAllocating a buffer of 64k bytes on the stack means that the stack overflow\ndetection (`caml_c_call`) won't have enough space to allocate 32k and will\nsegfault: see https://github.com/ocaml/ocaml/issues/7490 for a similar bug\nreport.\n\n`caml_c_call` has been properly fixed in behttps://github.com/ocaml/ocaml/pull/8670\nand it also has been changed to only allocate 4k -- also solving our initial\nissue with too small thread stacks (as 64+8<80).\n\nMany thanks to @sadiqj for helping with debugging the issue.\n\nCo-authored-by: Frédéric Bour <fred@tarides.com>","distinct":true,"url":"https://api.github.com/repos/mirage/index/commits/975139983456142f5489071a2c7db2b28453aeff"},{"sha":"f3bbda1d210925aae699ff84eaa7eb03f8f43c11","author":{"name":"Thomas Gazagnaire","email":"5f50a84c1fa3bcff146405017f36aec1a10a9e38@gazagnaire.org"},"message":"Merge pull request #132 from samoht/thread-stack\n\nDo not allocate 64k bytes buffers on the thread stack","distinct":true,"url":"https://api.github.com/repos/mirage/index/commits/f3bbda1d210925aae699ff84eaa7eb03f8f43c11"}]}
{"actor":{"display_login":"samoht"}}