9 Commits

Author	SHA1	Message	Date
nmlgc	a033b347fc	[Reduction] #44: graph_extmode	2014-08-15 16:12:09 +02:00
nmlgc	a313ae5d78	[Reduction] #43: Text VRAM variables	2014-08-15 14:26:44 +02:00
nmlgc	d95fc3cdd9	[Reduction] #32: get_machine	2014-08-14 14:48:55 +02:00
nmlgc	7b9a30fc8d	[Reduction] #31: get_machine_98	2014-08-14 14:30:48 +02:00
nmlgc	1c91cc75e7	[Reduction] #30: get_machine_at ... Um. Not sure if ZUN used an older version there, or if these additional branches simply resulted from a lack of optimization... And I even had to convert the labels to local syntax.	2014-08-14 14:27:36 +02:00
nmlgc	af609d5e1c	[Reduction] #29: get_machine_dosbox	2014-08-14 13:22:17 +02:00
nmlgc	59688e23fc	[Reduction] #28: Machine_State ... We~ll, OK, it's just a single variable, but it's originally stored in its own .ASM file as well. And yup, that's how we're going to treat data slices.	2014-08-14 13:22:14 +02:00
nmlgc	cc313d5095	[Reduction] #27: check_machine_fmr	2014-08-14 12:22:50 +02:00
nmlgc	534ba2d142	[Reduction] #5: bfill ... To get anywhere, we must become able to include assembly files that define their own segments. But this will only work if we include these files in the order they appear in in our dumps, *starting from the very first one*. And to include the very first one, we must first get rid of the erroneous references to the first few bytes of the data segment... and this function happens to be the first one referencing those.	2014-08-10 11:47:36 +02:00