|
@kornman00 : Thanks for your (lengthy) reply - I like the various suggestions you make.
I haven't coded out the preferred segment scanning yet, although it's definitely on my to-do list. As for using a cache for symbol-locations : Xeon was actually the first to use it (actually, it didn't have an automated function-finder, like Cxbx and Dxbx have). Cxbx uses a cache too, but I haven't implemented it for Dxbx yet.
About Symbol ordering... I don't know - can I really depend on each and every linker ever used, maintaining symbol-order?
As for the .sig format : If you do have some more information on it, please post it!
I ditched them, because it doesn't contain the cross-reference information that's present in the .pat files. Instead, they've used unique tuples of (offset + byte value) to differentiate a function between it's siblings.
|