View Single Post
  #2 (permalink)  
Old September 28th, 2004, 11:48 AM
davekw7x davekw7x is offline
Authorized User
 
Join Date: Feb 2004
Posts: 76
Thanks: 0
Thanked 0 Times in 0 Posts
Default

I Don't have your compiler/operating system, but I think I can explain stuff like this:

For Z/OS: try printing juulx with with %llX format, and see it gives all of the bytes (it does with Linux gcc).

For Windows: the formats you used for juuld and and juulx probably need to be something like %LLd or %Ld or something; the format that you are using apparently only prints out 32-bit values (the 32 least significants of the variable). What Windows compiler are you using?

Finally, note that the Windows output for juulb is the same as the z/OS, but the bytes are in reverse order (Intel, AMD, etc. CPUs running Windows are little-endian z/OS is apparently running on a CPU with big-endian mode).



Regards,

Dave
Reply With Quote