Again, the point that Al & Bitsavers weren't even contacted about this is fairly galling, and speaks to a policy of letting people with no real connection to or interest in vintage-computing preservation efforts be in charge of decisions over same. That does not inspire a great amount of confidence.
Maybe you could clarify, then, because frankly I've never been clear on just what the hey VCFed is or how it's associated with/separate from either this forum or the 'fests. Seems like the name just popped up outta nowhere some years back when the site was redesigned...
More than the compiler, I suspect the challenge would be adapting any large-scale C program written for a flat address space (particularly one that does in-depth memory management of its own) to a segmented model where any structure/heap of > 64 KB requires special handling just to access and...
Oh, very neat! I'm assuming this is essentially a CPU emulator core wrapped in a WINE-style system-call translation layer? (Of course, it wouldn't really require much "translation," but simply in terms of passing the call and response from the emulated environment to the host OS...)
I still use a 904HA running Devuan ascii as a "portable typewriter." The 1000s weren't as rock-solid as the 700-900 as far as build quality (nobody but nobody has solved the laptop hinge problem like whoever designed the Eee 900 series,) but hey, as long as it works!
Ditto on this. It's one thing in C where any project of moderate complexity is gonna have to compile to intermediate object files and link separately anyway, but there's no excuse for an assembler not to include this capability.