I think that the code cache should not be dynamically allocated with module_alloc (or module_alloc_update_bounds), because then it raises concerns about when / how to free that space. It is also redundant right now given that the code cache is a build-time fixed size. I think a nicer solution (for now) would be to statically allocate a number of rwx pages for the code cache. Then it's really part of Granary.
pgoodman
commented
9 years ago
I think that the code cache should not be dynamically allocated with
module_alloc(ormodule_alloc_update_bounds), because then it raises concerns about when / how to free that space. It is also redundant right now given that the code cache is a build-time fixed size. I think a nicer solution (for now) would be to statically allocate a number of rwx pages for the code cache. Then it's really part of Granary.