Date: | Tue, 27 Jun 2006 16:57:39 +0200 (CEST) |
---|---|
From: | Enric Herrero <enricherrero@xxxxxxxx> |
Subject: | Re: [Gems-users] Node number limitations? |
Hi, Thank you for answering. We use a 32 bit processor and despite setting the file to #define __32BITS__ is still not working. We have also problems with the number of memories used and seems to be the same kind of problem. When we use 64 processors and we try to access node 55 it is going to node 23. Desired node 55 -> 110111As we see ruby seems to use less bits than the necessary for dealing with this number of memories. We have seen that in OptBigSet.C when the vectors are defined some masks are applied. Why are these masks applied? We don't understand the sentence: // the number of populated spaces in the higest-order array slot is: // m_nSize % 32, so the uppermost 32 - m_nSize%32 bits should be // cleared Is this related to our problem? And if it has relation it is possible to increase the number of bits used? Thank you /Marco and Enric Dan Gibson <degibson@xxxxxxxx> escribió: Marco/Enric,
LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | Re: [Gems-users] atomic bus, Mike Marty |
---|---|
Next by Date: | Re: [Gems-users] Ruby debugging and assert failure, Bradford Beckmann |
Previous by Thread: | Re: [Gems-users] Node number limitations?, Dan Gibson |
Next by Thread: | Re: [Gems-users] Node number limitations?, Dan Gibson |
Indexes: | [Date] [Thread] |