The intrinsics that *need* to be inlined (as opposed to procedure calls) in my mind are:
- Load and store barriers - Constant-sized allocations (for bump allocations) - return operations on architectures that do not implement a return instruction (which DBT can already catch). - stack space check - making sure we have room for a new frame on a possibly segmented stack. The intrinsics that *may *want to be inlined in some cases are: - GCPoll (mutator thread polling for GC coordination) I can think of a whole bunch of other communications from the mutator to the collector, but I can't think of any that are so performance critical that they warrant inlining. I can also think of a bunch of mechanisms by which the collector interrogates the state of a [possibly temporarily] paused mutator, but those don't seem likely to involve DBT-style inlining tricks. Can anybody think of intrinsic[s] that need to be inlined that I haven't identified above?
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
