juj wrote: > Yeah, let me be clear here: I see the GLib problem as being a completely > separate problem from the one you have. AFAICS this patch doesn't attempt to > address your issue at all, and the solutions I'm brainstorming here also > don't attempt to address the issue.
Thanks, that makes sense, agreed. > also for b), have you filed a bug on Chrome with that as a feature request? I did, though unfortunately it was closed on the basis of being too costly to implement. I got started on an Emscripten SAFE_HEAP style codegen pass to wrap each generated function pointer dispatch, but it was quite tricky to implement from Emscripten repository side alone. https://github.com/llvm/llvm-project/pull/153168 _______________________________________________ cfe-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
