5 ms·

Looks like 64 bit support is his main goal. Sounds like lots of pointer arithmetic in there that doesn't port well. Agree that they'll definitely have to learn

• fhars 5y ago
  No, the original code supports Alpha, so it should be 64bit clean. It's got loads of other issues, though. Not respecting sequence points seems to be the most obvious.
  • sargstuff 5y ago
    Al, yeah, but does Alpha handle addresses boundaries on 1,2,3,4 byte boundaries. If its, more than one, it might compile, but will not run. https://gcc.gnu.org/onlinedocs/gcc-3.2/gcc/Variable-Attributes.html https://gcc.gnu.org/onlinedocs/gcc-3.2/gcc/Variable-Attribut...
• sargstuff 5y ago
  Some implicit hardware references implied by use of C casts. C compiler doesn't guarantee bit spacing/alignment in strucs. (*char) is used to force pointer address inside of a struct to align on byte boundary which is not true of all hardware! aka adresses allignment may need to be 16, 32, or 64.