ReC98

Commit Graph

Author	SHA1	Message	Date
nmlgc	40de176f2c	[Reduction] #191 : bcloser	2014-08-26 20:54:57 +02:00
nmlgc	4a36dd15de	[Reduction] #159 : super_entry_bfnt [Binary change] Order of 5 relocations in TH05's MAIN.EXE.	2014-08-23 18:09:23 +02:00
nmlgc	8b32104540	[Reduction] #131-134: graph_pi_load_pack Second biggest master.lib object right there... and apparently, TASM doesn't support segment prefixes in EQU directives? And yes, there really is no viable solution for both the NOPCALL problem (the TASM manual states that these NOPs are inserted during single-pass assembly, which we can't do) and the complementary jump sequences (which are only inserted for forward references when specifying the JUMPS directive, which doesn't seem to work for us either).	2014-08-22 21:15:44 +02:00

Author

SHA1

Message

Date

nmlgc

40de176f2c

[Reduction] #191 : bcloser

2014-08-26 20:54:57 +02:00

nmlgc

4a36dd15de

[Reduction] #159 : super_entry_bfnt

[Binary change] Order of 5 relocations in TH05's MAIN.EXE.

2014-08-23 18:09:23 +02:00

nmlgc

8b32104540

[Reduction] #131-134: graph_pi_load_pack

Second biggest master.lib object right there... and apparently, TASM doesn't
support segment prefixes in EQU directives?

And yes, there really is no viable solution for both the NOPCALL problem (the
TASM manual states that these NOPs are inserted during single-pass assembly,
which we can't do) and the complementary jump sequences (which are only
inserted for forward references when specifying the JUMPS directive, which
doesn't seem to work for us either).

2014-08-22 21:15:44 +02:00

3 Commits