<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> Hi,<div><br><div><div>On 21 Mar 2008, at 10:08, radsci2008 wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">intended for only the 32-bit version, a comment to that effect might</font></p> <p style="margin: 0.0px 0.0px 0.0px 0.0px"><font face="Helvetica" size="3" style="font: 12.0px Helvetica">be added to the respective arch files to indicate that.</font></p> </blockquote></div><br></div><div>maybe Juerg was not clear enough yesterday. We're talking about the integer representation not</div><div>the reals. CP2K works perfectly for 64-bit REALS (DOUBLE PRECISION in the case of a 32-bit representation for REAL and INTEGER).</div><div><br class="webkit-block-placeholder"></div><div>Moreover, I could be wrong, but I don't see any reason why a 64-bit default INTEGER g95 should give better results than 32-bit default INTEGER.</div><div>well yes.. It consumes MUCH more memory.. if you like that..</div><div><br></div><div>Be safe and use the standard fortran version of g95: <a href="http://ftp.g95.org/g95-x86_64-64-linux.tgz">http://ftp.g95.org/g95-x86_64-64-linux.tgz</a></div><div>When there will be around a compiler with standard 64-bit representation (in which double precision will be 128-bit long) then we can discuss again about that.. for the time being if you wanna use 64-bit for integers and 64-bit for double precision.. well.. it's your problem..</div><div><br class="webkit-block-placeholder"></div><div>Teo</div><div><br class="webkit-block-placeholder"></div></body></html>