Thank you John. Yes I already compiled PETSc, I'm going to try those flags
for libmesh and update here for future reference if necessary.



On Mon, Nov 11, 2013 at 7:08 PM, John Peterson <[email protected]> wrote:

>
>
>
> On Mon, Nov 11, 2013 at 4:37 PM, Santiago Alonso Pérez Rubiano <
> [email protected]> wrote:
>
>> Has anyone tried (or succeeded at) compiling libmesh on native mode for
>> Xeon Phi?
>>
>
>
> Yes, we've had some success:  we cross-compiled, used the Intel
> compilers/MPI, and a TBB built for MIC.
>
> Here's a configure line you might start with...
>
> configure libmesh_CFLAGS="-mmic" \
> libmesh_CXXFLAGS="-DMPICH_SKIP_MPICXX -DTBB_DEPRECATED=1 -mmic" \
> libmesh_CPPFLAGS="-DMPICH_SKIP_MPICXX -DTBB_DEPRECATED=1 -mmic" \
> CFLAGS="-mmic" \
> CXXFLAGS="-mmic" \
> --host=x86_64-k1om-linux \
> --enable-static \
> --with-cc=mpiicc \
> --with-cxx=mpiicpc \
> --with-fc=mpiifort \
> --disable-shared \
> --prefix=/some/location/libmesh \
> --with-tbb-lib=/global/opt/intel/composer_xe_2013.4.183/tbb/lib/mic \
> --with-tbb=/global/opt/intel/composer_xe_2013.4.183/tbb \
> --with-methods="opt" \ --enable-openmp
>
> The prefix should probably be some directory "visible" from the Phi card.
>
> Note the --host argument.  This triggers cross-compiling, but I'm not too
> sure how important the actual argument is... it is mainly to prevent
> autoconf from testing for the existence of certain files...
>
> Have you already compiled PETSc for Phi?  If not, that would probably be a
> good first step.
>
> --
> John
>
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most 
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to