For clarity, it's also fine if these symbols get renamed/changed/etc, exporting them doesn't imply any future compatibility, it's just best-effort. Without the export it's very difficult and hacky to get to them, which translates to cas...Eregon (Benoit Daloze)
+1, this would make external profilers more reliable (there are several important advantages of external profilers, e.g. reduce a lot the observer effect, no need to change anything in the already-running program). Datadog is shipping t...Eregon (Benoit Daloze)
iseq.h does not reference any of the pm_* types or functions declared in prism_compile.h, so include the latter from the files that actually use it instead. Only 6 of the 19 files including iseq.h need the prism declarations, so this kee...Eregon (Benoit Daloze)
There have been new methods/classes in the last week like: `IO::Buffer#advance` https://github.com/ruby/ruby/pull/19122 `Introduce IO::Buffer::Storage and parent-relative slice views` https://github.com/ruby/ruby/pull/19186 I thin...Eregon (Benoit Daloze)
I think maybe the bigger issue here is that profiling a program using YJIT or ZJIT might give very misleading results, because the action of profiling itself (if the profiler uses postponed jobs and many do) has the unexpected side effec...Eregon (Benoit Daloze)
Draft of a potential fix: https://github.com/ruby/ruby/pull/18205 I have tried several things to avoid overhead on the the no-interrupt-path but they mostly failed, I guess the YJIT backend doesn't really support generating code with ...Eregon (Benoit Daloze)
Eregon (Benoit Daloze)08:36 AM Ruby Feature #21539: Export symbols for external profiling of stripped shared Ruby builds