> The recent change to boost/cstdint.hpp for Cray systems is not
> appropriate for the Cray X1. It has a 16-bit short type, however there
> are performance penalties associated with it.
OK thanks, patches applied.
> The following patch for cstdint.hpp sets up the appropriate typedefs for
> this p
On Thursday, January 23, 2003, at 07:14 PM, Dan Gohman wrote:
Hi Matthias,
The reason for special-casing the Cray X1 here is so that int_fast16_t
isn't defined to be short, as short has performance penalties
associated
with it on this platform.
Hi Dan,
I missed that point. Yes, you are right
Hi Matthias,
The reason for special-casing the Cray X1 here is so that int_fast16_t
isn't defined to be short, as short has performance penalties associated
with it on this platform.
I can't guarantee I'll be able to test jam, but I'll let you know if I
get to it.
Dan
On Thu, 2003-01-23 at 11:4
Hi Dan,
I don't think this will be needed since on the X1 USHRT_MAX should be
0x, and thus the default version will work. Note that the patch for
the SV1 and other Crays that I submitted checks for USHRT_MAX being
0x and thus does not apply on the X1 anyways.
On another note, I got
The recent change to boost/cstdint.hpp for Cray systems is not
appropriate for the Cray X1. It has a 16-bit short type, however there
are performance penalties associated with it.
The following patch for cstdint.hpp sets up the appropriate typedefs for
this platform.
diff -u -r1.29 cstdint.hpp
--