BorlandTalk.com

Guest

This is old stuff....

But I observe the TLINK that shipped with the BC++ 4.5 package behaving
rather badly when trying to link something that includes OBJ's that use
threaded fixups. Lots of fixup overflow error messages an completely
disfunctional EXE. Using MS's LINK makes the problem go away

Has anyone else observed this?

As a part of a much larger OBJ utility project, this TLINK behavior recently
prompted me to implement a threaded fixup "de-optimizer" that will remove
the threaded fixups and replace them with their non-threaded (but plumper)
equivalents.

Is anyone willing to help with the testing on this thread de-optimization
gadget?

The tool does a whole slew of other interesting things with OBJ's as well as
this thread stuff. It includes a TDUMP'ish kind of OBJ display mode to dump
out OBJ's, can add some patch space into a segment, diddle names, add new
PUBDEF/EXTDEF aliases, combine EXTDEF/LNAMES more efficiently into a single
OMF record (TASM is a real offender here), fix bad checksum values, fix the
busted 64K "big bit" that MASM got wrong for about 8 or 9 years.

There's also support in it for PharLap's Easy OMF 386 extensions that I
can't even try since I don't have that product on hand. If someone does,
that would be very nice...