@Nash: You're template still works fine with some modification to fit the latest GDCC builds, I just needed a bit of help getting it there. When I get it all sorted out, I'll share the changes with you if you want to update the template post; maybe split it into an ACS template and a C template?
@TZK: That batch works with just a few tweaks, most of which need reverted to make it generic enough for a template; I don't generally edit my PATH variable so giving the batch a direct route to GDCC is imperative.
Two questions remain:
1 - Why two files now? I assume the libc file is the standard C stuff I use and the other is my own source, but can we combine them together like in the past for just one library?
2 - (I think this is an optimization question) Older builds of my source required an edit to the ACS-VM at the source level to increase the instruction count so the code wasn't considered an infinite loop. That worked fine until today when the compiled code suddenly started getting killed by the VM again. So my question is, what is the following line from the batch instructing GDCC to do, and especially what are those parameters and could they be related to my sudden instruction count issue?
- Code: Select all • Expand view
gdcc-ld --bc-target=ZDoom --bc-zdacs-init-delay --alloc-min Sta "" 1000000000 ir/libc.ir ir/libGDCC.ir acs/libc.bin
edit: @TZK a thank you is also in order, so thank you my good fellow!