Its not so much the bitness as the compiler. For example, if I built in dbg mode with the intel compiler this wouldn't necessarily happen, or perhaps even a different version of the same compiler.
-Ben ________________________________ From: Yujie <[email protected]> To: Kirk, Benjamin (JSC-EG311) Cc: [email protected] <[email protected]>; Roy Stogner <[email protected]> Sent: Thu Jan 28 08:57:51 2010 Subject: Re: [Libmesh-users] Fwd: further data Re: weird problem Sorry for reply late. However, why is it ok for Intel 32bits Debug mode? There is not problem on 32bits-based cluster. Thanks a lot. Regards, Yujie On Wed, Jan 27, 2010 at 2:42 PM, Kirk, Benjamin (JSC-EG311) <[email protected]<mailto:[email protected]>> wrote: > I got the different cost time using "METHOD=pro" and "METHOD=dbg". You can > find the details from the following tables. In "dbg", the problem is always > there. However, in "pro", the problem disapears. Any advice? In this case, I > run the codes for both in slave node. Thanks a lot. Whoops, probably should have asked this long ago - you were always running with METHOD=dbg? What about METHOD=opt?? It very well could be that some pedantic error checking in that method are causing the problem. G++ with pedantic internal C++-library error checking can turn order log(N) operations to linear(N), and I've run into this before.... -Ben ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
