[Info-vax] Hard links on VMS ODS5 disks

[John Reagan]

On Saturday, July 22, 2023 at 8:52:28 PM UTC-4, Stephen Hoffman wrote:
> On 2023-07-22 20:57:03 +0000, John Reagan said: 
> > 
> > Simple? Try to deal with condition codes. Try to deal with routines 
> > that jump between each other. Try to make the stack "look like a VAX" 
> > on platforms that say otherwise. :)
> Kinda wonder what radare2 would do with that stress test, err, with 
> that xMacro32 executable. 
> 
> Semi-related is XTRAN, and which has been discussed before: 
> http://www.xtran-llc.com/vxmcee.html 
> http://www.xtran-llc.com/xtran.html#reengrg 
> 
> -- 
> Pure Personal Opinion | HoffmanLabs LLC

The real ugly Macro-32 sources include LAD driver and the shadow driver.
When we did the Itanium compiler, I had the compilers print out some
internal counters into the .LIS file.  We were dealing with routines that
enter in one places with one set of arguments and then jumped to another
routine and returned from another routine's epilogue.  There are issues dealing
with NaTs and such.  From what I can tell, EVERY .CALL_ENTRY and .JSB_ENTRY
in the shadow driver can exist from EVERY possible RET.  Of course, in real life
I'm sure the data doesn't do that, but Macro had to worry about it.  I'm not sure
I could prepare myself for the XTRAN version of the shadow driver.