Rooba
/
ReC98
mirror of https://github.com/nmlgc/ReC98.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity
ReC98/th01/hardware/egccopyr.cpp

26 lines
642 B
C++
Raw Normal View History

[Maintenance] Move the EGC copy setup function to a separate file Too bad we still have to bother with renaming the function via #define in the few cases where an executable contains two or more copies of this function. We can't just make it `static`, since TH02 MAINE.EXE actually does far-call it from a different segment (and thus, translation unit). Part of P0094, funded by Yanga.
2020-05-23 16:20:56 +00:00
#include "th01/hardware/egcscopy.c"
[C decompilation] [th01] VRAM region copy via EGC The same function appears unused in TH02's MAINE.EXE. Separate commit because this was painful enough and we can link the C version into FUUIN.EXE right now.
2015-02-27 22:11:47 +00:00
[Maintenance] Declare distinct types for pixel and VRAM sizes Oh wait, we also need one of those for an upcoming structure! Part of P0111, funded by [Anonymous] and Blue Bolt.
2020-08-21 18:13:08 +00:00
void egc_copy_rect_1_to_0_16(screen_x_t x, vram_y_t y, pixel_t w, pixel_t h)
[C decompilation] [th01] VRAM region copy via EGC The same function appears unused in TH02's MAINE.EXE. Separate commit because this was painful enough and we can link the C version into FUUIN.EXE right now.
2015-02-27 22:11:47 +00:00
{
[Maintenance] Declare distinct types for screen, VRAM, and TRAM coordinates Whew, time to look at every `int` variable we ever declared! The best moment to do this would have been a year ago, but well, better late than never. No need to communicate that in comments anymore. These shouldn't be used for widths, heights, or sprite-space coordinates. Maybe we'll cover that another time, this commit is already large enough. Part of P0111, funded by [Anonymous] and Blue Bolt.
2020-08-20 19:59:45 +00:00
register screen_x_t x_end = x;
register screen_x_t x_floor = x_end;
[Maintenance] Declare distinct types for pixel and VRAM sizes Oh wait, we also need one of those for an upcoming structure! Part of P0111, funded by [Anonymous] and Blue Bolt.
2020-08-21 18:13:08 +00:00
pixel_t row;
[Maintenance] Declare distinct types for screen, VRAM, and TRAM coordinates Whew, time to look at every `int` variable we ever declared! The best moment to do this would have been a year ago, but well, better late than never. No need to communicate that in comments anymore. These shouldn't be used for widths, heights, or sprite-space coordinates. Maybe we'll cover that another time, this commit is already large enough. Part of P0111, funded by [Anonymous] and Blue Bolt.
2020-08-20 19:59:45 +00:00
screen_x_t col;
[Maintenance] Declare a distinct type for VRAM offsets … and this one, while I'm at it. I've been using pretty much every possible type for VRAM offset variables, depending on my mood that day, since signedness apparently never matters for those. Except that it does. And so, just like with most of our high-level types, we also have to account for ZUN's little signedness inconsistencies here. Oh well, at least it's now only one of two types, and there's no need to choose between `int` or `unsigned int` or `short` or `unsigned short` or `int16_t` or `uint16_t` or `size_t` or… Part of P0111, funded by [Anonymous] and Blue Bolt.
2020-08-21 17:18:28 +00:00
vram_offset_t row_p;
[Maintenance] Use `dots` for 1bpp lines, and `planar` for B/R/G/E dot structs I tried `brge` for the latter, but that had *the* most horrible ergonomics, and I misspelled it as `bgre` 100% of the times I typed it manually. Turns out that `dots` is also consistent with master.lib's naming scheme, leaving `planar` to *actually* refer to types storing multiple planes worth of pixels. These types are showing up more and more, and deserve something better than their previous long-winded and misleading name. Part of P0081, funded by Ember2528.
2020-03-06 23:25:03 +00:00
dots16_t dots;
[Maintenance] Declare a distinct type for VRAM offsets … and this one, while I'm at it. I've been using pretty much every possible type for VRAM offset variables, depending on my mood that day, since signedness apparently never matters for those. Except that it does. And so, just like with most of our high-level types, we also have to account for ZUN's little signedness inconsistencies here. Oh well, at least it's now only one of two types, and there's no need to choose between `int` or `unsigned int` or `short` or `unsigned short` or `int16_t` or `uint16_t` or `size_t` or… Part of P0111, funded by [Anonymous] and Blue Bolt.
2020-08-21 17:18:28 +00:00
vram_offset_t p;
[Maintenance] Fix any whitespace issues in our own code
2015-09-07 13:44:02 +00:00
[C decompilation] [th01] VRAM region copy via EGC The same function appears unused in TH02's MAINE.EXE. Separate commit because this was painful enough and we can link the C version into FUUIN.EXE right now.
2015-02-27 22:11:47 +00:00
x_end += w;
x_floor &= 0xFFF0;
[Maintenance] Use inline functions for all VRAM offset calculations At least those can all be moved to a single place. Part of P0105, funded by Yanga.
2020-06-16 10:43:39 +00:00
row_p = vram_offset_shift(x_floor, y);
[C decompilation] [th01] VRAM region copy via EGC The same function appears unused in TH02's MAINE.EXE. Separate commit because this was painful enough and we can link the C version into FUUIN.EXE right now.
2015-02-27 22:11:47 +00:00
egc_start_copy();
for(row = 0; row < h; row++) {
for(col = x_floor, p = row_p; col < x_end; p += 2, col += 16) {
[Maintenance] Use `dots` for 1bpp lines, and `planar` for B/R/G/E dot structs I tried `brge` for the latter, but that had *the* most horrible ergonomics, and I misspelled it as `bgre` 100% of the times I typed it manually. Turns out that `dots` is also consistent with master.lib's naming scheme, leaving `planar` to *actually* refer to types storing multiple planes worth of pixels. These types are showing up more and more, and deserve something better than their previous long-winded and misleading name. Part of P0081, funded by Ember2528.
2020-03-06 23:25:03 +00:00
graph_accesspage_func(1); VRAM_SNAP(dots, B, p, 16);
graph_accesspage_func(0); VRAM_PUT(B, p, dots, 16);
[C decompilation] [th01] VRAM region copy via EGC The same function appears unused in TH02's MAINE.EXE. Separate commit because this was painful enough and we can link the C version into FUUIN.EXE right now.
2015-02-27 22:11:47 +00:00
}
[Maintenance] #define the number of dots in a byte One fewer magic number. And one more deliberate dependency on a PC-98-specific hardware constant, to further drive home just how unportable these games are, even once decompilation will be complete. Part of P0105, funded by Yanga.
2020-08-05 21:04:47 +00:00
row_p += ROW_SIZE;
[C decompilation] [th01] VRAM region copy via EGC The same function appears unused in TH02's MAINE.EXE. Separate commit because this was painful enough and we can link the C version into FUUIN.EXE right now.
2015-02-27 22:11:47 +00:00
}
egc_off();
}