John Maddock wrote:
I'll commit that, but I would prefer to make the test Cray specific as well
as testing for #ifdef USHRT_MAX == 0x, is there some macro that the
Cray compiler defines?
On the Cray T3D, Cray T3E, and Cray SV1, _CRAYT3D, _CRAYT3E, and
_CRAYSV1 are defined.
On the Cray
On Saturday, January 18, 2003, at 10:33 PM, David Abrahams wrote:
ii) the fast vector units do not help anything for compiling the code.
Just one question: why the heck don't they make a cross-compiler which
runs on a machine better-suited to compilation?
They have that, but it costs extra m
Matthias Troyer <[EMAIL PROTECTED]> writes:
> On Saturday, January 18, 2003, at 07:36 PM, Daniel Yerushalmi wrote:
>
>>
>> I'll try to do it at least once to see which parts of boost we can use,
>> and see how much CPU time this gobbles up. If it is not too much, I
>> will talk to our sysadmins i
On Saturday, January 18, 2003, at 07:36 PM, Daniel Yerushalmi wrote:
I'll try to do it at least once to see which parts of boost we can use,
and see how much CPU time this gobbles up. If it is not too much, I
will talk to our sysadmins if they would allow me to do it about once a
month. I don't
I'll try to do it at least once to see which parts of boost we can use,
and see how much CPU time this gobbles up. If it is not too much, I
will talk to our sysadmins if they would allow me to do it about once a
month. I don't think that testing more often would be possible, since
already compilin
