Hi all.<br>
<br>
Of course I want SSE enabled. There is no sense in benching it against
different compilers if in one you enable the speed and on the other,
and in the other you remove almost every optimization. That's why in
the last message I've sent the eror I'm getting in the compilation:<br>
<br>
<span class="q">
*************************************************************************************************************************************<br>
<div>
/bin/sh ../../../../libtool --mode=compile /usr/bin/gcc -O3
-ffast-math -funroll-all-loops -fpeel-loops -c -o
nb_kernel010_x86_64_sse.lo nb_kernel010_x86_64_sse.s<br>
libtool: compile: unable to infer tagged configuration<br>
libtool: compile: specify a tag with `--tag'<br>
make[5]: ** [nb_kernel010_x86_64_sse.lo] Erro 1<br>
*************************************************************************************************************************************<br>
<br>
That's ther error that arises from enabling SSE, and doesn't seems to
be related to it (despite it doesn't make too much sense, since it's
what is enabled), but only to some kind of libtool option not being
corretly passed. From what I could get from the internet, it's related
to the swithings in the compiler being used during the compilation
process, but I could not get a proper way to get around it for gromacs.
And I do think this is last error in the compilations in the way to get
a fully working executable gromacs package compiled with the intel
compilers on AMD64 machines. The others are just warnings (which didn't
look too nice for me anyway, but also can mean nothing), which can be
thought about later.<br>
</div></span><br>
Does anybody knows how to go around this specific error? Is it a known issue in gromacs, under some kind of different subject?<br>
<br>
Thank you all for all the help in advance. :)<br>
<br>
Jones<br>
<br><div><span class="gmail_quote">On 6/2/06, <b class="gmail_sendername">Erik Lindahl</b> <<a href="mailto:lindahl@sbc.su.se">lindahl@sbc.su.se</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>> Erik: I'm sure about the flags. Not using the ones for SSE3,<br>> despite my processor having those. I'll just try to activate those<br>> as soon as I get a compiling procedure. By now, I even using the --
<br>> disable-x86-64-sse flag for configure, just to be sure. ;) Also, I<br>> tried the "CC_FOR_BUILD=gcc" environment, but despite it has gone<br>> throw the invsqrt compilation, I looked in and it was compiling
<br>> everything with gcc, and nothing with icc. :(<br>You so do NOT want to do disable SSE in Gromacs. To get the extra 2%<br>performance from Intel icc you just killed the assembly loops which<br>will reduce your performance by roughly 50%.
<br><br>The Gromacs SSE code is completely portable, and checks if the<br>instructions are supported at runtime.<br>> Yang: Yes, I'm using the intel compiler with emt64. I reinstalled<br>> the software step by step specifically to be sure about this point.
<br>> And I understand that gromacs has an assembly core, and that this<br>> is basically the "heart" of the program speed. But, even thow,<br>> 5-10% means something, and every nano-second counts. Specially when
<br>> you have a big delay to deal with, and that this 10% mean<br>> 0.25ns. ;) Even then, after I successfully compile it we will be<br>> able to say for sure how much if extra performance (if it yelds<br>> any) does the intel compiler gives on AMD64 machines. Moreover, as
<br>> I said in a long time ago message: I want to use QM/MM with gromacs<br>> +cpmd, and at this point I really dislike the idea of compiling one<br>> thing with intel (cpmd) and the other with gcc (gromacs). Since I
<br>> can't make cpmd work on gcc, I'm trying to make gromacs work on<br>> intel. ;)<br>We have already tried the intel compiler multiple times (both on ia32<br>and x86-64 platforms), and it gets you roughly 2% extra performance
<br>in Gromacs.<br><br>A really nice thing with icc is that the object format is completely<br>gcc-compatible, so there shouldn't be any problems mixing.<br><br>Cheers,<br><br>Erik<br>
</blockquote></div>