August 2013 - devel - mailman3.cels.anl.gov

Re: [mpich-devel] Message Passing models for Hybrid Parallelism
by Huiwei Lu 29 Aug '13

29 Aug '13

Thank you Shigang. Your links are very helpful. Sorry Muhammad I didn't answer your question at the first time. I have just read about HMPI briefly several days ago. Huiwei Lu http://www.mcs.anl.gov/~huiweilu/ On Thu, Aug 29, 2013 at 1:53 PM, Shigang Li <shigangli.cs(a)gmail.com> wrote: > Hi Muhammad, Huiwei, > > There is a Hybrid MPI(HMPI) library which aims at implementing MPI efficiently > on both inter-node network and shared memory architecture. Here are some > papers talking about this, which may give you some info. > > Ownership Passing: Efficient Distributed Memory Programming on Multi-core > Systems<http://htor.inf.ethz.ch/publications//img/friedley-ownership-passing.pdf> > NUMA-Aware Shared Memory Collective Communication for MPI<http://dl.acm.org/citation.cfm?id=2462903> > Hybrid MPI: Efﬁcient Message Passing for Multi-core Systems<http://htor.inf.ethz.ch/publications//img/friedley-hmpi-sc13.pdf> > > Best Regards, > Shigang > > > On Thu, Aug 29, 2013 at 12:31 PM, Muhammad Ansar Javed < > muhammad.ansar(a)seecs.edu.pk> wrote: > >> Hi Huiwei, >> Thank you so much for suggesting reading material. These are really >> useful papers but I am looking for models that provide seamless integration >> of two devices (Network device and Shared Memory device) into one hybrid >> device. Message passing mechanism should be exactly same for end user at >> MPI layer. >> Idea is to use to use Network Device for establishing network >> communication between nodes and Shared memory device should >> be responsible for Intra-node communication on each multi-core machine. >> Shared Memory device is implemented using Multi-threading approach. Both >> Network and Shared Memory device are in working state independently. >> >> I hope it explains what I am really looking for. Please suggest papers >> that can provide guidelines for achieving this goal. >> >> >> >> On Wed, Aug 28, 2013 at 7:40 PM, Huiwei Lu <huiweilu(a)mcs.anl.gov> wrote: >> >>> Hi, Muhammad, >>> >>> As I am also starting to exploit this area, I would like to share with >>> you some of my readings. >>> >>> Following are a few papers to help you start: >>> 1. Early Experiments with the OpenMP/MPI Hybrid Programming Model, >>> http://www.mcs.anl.gov/~lusk/hybridpaper.pdf >>> 2. Test Suite for Evaluating Performance of MPI Implementations That >>> Support MPI THREAD MULTIPLE, >>> http://www.mcs.anl.gov/~thakur/papers/thread-tests.pdf >>> >>> In the second paper, you can also find some code examples for using >>> hybrid programming model. >>> >>> Best, >>> >>> Huiwei Lu >>> http://www.mcs.anl.gov/~huiweilu/ >>> >>> >>> On Wed, Aug 28, 2013 at 12:54 AM, Muhammad Ansar Javed < >>> muhammad.ansar(a)seecs.edu.pk> wrote: >>> >>>> Hi, >>>> I am looking for message passing models for Hybrid Parallelism that are >>>> being used in MPICH implementations for the Cluster of Multi-core machines. >>>> Can you please suggest me some papers or study material that can explain >>>> communication models that incorporate network communication as well as >>>> shared memory communication. >>>> >>>> Thanks, >>>> Ansar >>>> >>> >>> >> >> >> -- >> >> Regards: >> * >> *Muhammad Ansar Javed >> NUST SEECS >> Contact: +92 334 438 9394 >> Email: muhammad.ansar(a)seecs.edu.pk >> > >

1 0

Re: [mpich-devel] Message Passing models for Hybrid Parallelism
by Shigang Li 29 Aug '13

29 Aug '13

Hi Muhammad, Huiwei, There is a Hybrid MPI(HMPI) library which aims at implementing MPI efficiently on both inter-node network and shared memory architecture. Here are some papers talking about this, which may give you some info. Ownership Passing: Efficient Distributed Memory Programming on Multi-core Systems<http://htor.inf.ethz.ch/publications//img/friedley-ownership-passing.pdf> NUMA-Aware Shared Memory Collective Communication for MPI<http://dl.acm.org/citation.cfm?id=2462903> Hybrid MPI: Efﬁcient Message Passing for Multi-core Systems<http://htor.inf.ethz.ch/publications//img/friedley-hmpi-sc13.pdf> Best Regards, Shigang On Thu, Aug 29, 2013 at 12:31 PM, Muhammad Ansar Javed < muhammad.ansar(a)seecs.edu.pk> wrote: > Hi Huiwei, > Thank you so much for suggesting reading material. These are really useful > papers but I am looking for models that provide seamless integration of two > devices (Network device and Shared Memory device) into one hybrid device. > Message passing mechanism should be exactly same for end user at MPI > layer. > Idea is to use to use Network Device for establishing network > communication between nodes and Shared memory device should > be responsible for Intra-node communication on each multi-core machine. > Shared Memory device is implemented using Multi-threading approach. Both > Network and Shared Memory device are in working state independently. > > I hope it explains what I am really looking for. Please suggest papers > that can provide guidelines for achieving this goal. > > > > On Wed, Aug 28, 2013 at 7:40 PM, Huiwei Lu <huiweilu(a)mcs.anl.gov> wrote: > >> Hi, Muhammad, >> >> As I am also starting to exploit this area, I would like to share with >> you some of my readings. >> >> Following are a few papers to help you start: >> 1. Early Experiments with the OpenMP/MPI Hybrid Programming Model, >> http://www.mcs.anl.gov/~lusk/hybridpaper.pdf >> 2. Test Suite for Evaluating Performance of MPI Implementations That >> Support MPI THREAD MULTIPLE, >> http://www.mcs.anl.gov/~thakur/papers/thread-tests.pdf >> >> In the second paper, you can also find some code examples for using >> hybrid programming model. >> >> Best, >> >> Huiwei Lu >> http://www.mcs.anl.gov/~huiweilu/ >> >> >> On Wed, Aug 28, 2013 at 12:54 AM, Muhammad Ansar Javed < >> muhammad.ansar(a)seecs.edu.pk> wrote: >> >>> Hi, >>> I am looking for message passing models for Hybrid Parallelism that are >>> being used in MPICH implementations for the Cluster of Multi-core machines. >>> Can you please suggest me some papers or study material that can explain >>> communication models that incorporate network communication as well as >>> shared memory communication. >>> >>> Thanks, >>> Ansar >>> >> >> > > > -- > > Regards: > * > *Muhammad Ansar Javed > NUST SEECS > Contact: +92 334 438 9394 > Email: muhammad.ansar(a)seecs.edu.pk >

1 0

Re: [mpich-devel] Message Passing models for Hybrid Parallelism
by Muhammad Ansar Javed 29 Aug '13

29 Aug '13

Hi Huiwei, Thank you so much for suggesting reading material. These are really useful papers but I am looking for models that provide seamless integration of two devices (Network device and Shared Memory device) into one hybrid device. Message passing mechanism should be exactly same for end user at MPI layer. Idea is to use to use Network Device for establishing network communication between nodes and Shared memory device should be responsible for Intra-node communication on each multi-core machine. Shared Memory device is implemented using Multi-threading approach. Both Network and Shared Memory device are in working state independently. I hope it explains what I am really looking for. Please suggest papers that can provide guidelines for achieving this goal. On Wed, Aug 28, 2013 at 7:40 PM, Huiwei Lu <huiweilu(a)mcs.anl.gov> wrote: > Hi, Muhammad, > > As I am also starting to exploit this area, I would like to share with you > some of my readings. > > Following are a few papers to help you start: > 1. Early Experiments with the OpenMP/MPI Hybrid Programming Model, > http://www.mcs.anl.gov/~lusk/hybridpaper.pdf > 2. Test Suite for Evaluating Performance of MPI Implementations That > Support MPI THREAD MULTIPLE, > http://www.mcs.anl.gov/~thakur/papers/thread-tests.pdf > > In the second paper, you can also find some code examples for using hybrid > programming model. > > Best, > > Huiwei Lu > http://www.mcs.anl.gov/~huiweilu/ > > > On Wed, Aug 28, 2013 at 12:54 AM, Muhammad Ansar Javed < > muhammad.ansar(a)seecs.edu.pk> wrote: > >> Hi, >> I am looking for message passing models for Hybrid Parallelism that are >> being used in MPICH implementations for the Cluster of Multi-core machines. >> Can you please suggest me some papers or study material that can explain >> communication models that incorporate network communication as well as >> shared memory communication. >> >> Thanks, >> Ansar >> > > -- Regards: * *Muhammad Ansar Javed NUST SEECS Contact: +92 334 438 9394 Email: muhammad.ansar(a)seecs.edu.pk

1 0

Re: [mpich-devel] Message Passing models for Hybrid Parallelism
by Huiwei Lu 28 Aug '13

28 Aug '13

Hi, Muhammad, As I am also starting to exploit this area, I would like to share with you some of my readings. Following are a few papers to help you start: 1. Early Experiments with the OpenMP/MPI Hybrid Programming Model, http://www.mcs.anl.gov/~lusk/hybridpaper.pdf 2. Test Suite for Evaluating Performance of MPI Implementations That Support MPI THREAD MULTIPLE, http://www.mcs.anl.gov/~thakur/papers/thread-tests.pdf In the second paper, you can also find some code examples for using hybrid programming model. Best, Huiwei Lu http://www.mcs.anl.gov/~huiweilu/ On Wed, Aug 28, 2013 at 12:54 AM, Muhammad Ansar Javed < muhammad.ansar(a)seecs.edu.pk> wrote: > Hi, > I am looking for message passing models for Hybrid Parallelism that are > being used in MPICH implementations for the Cluster of Multi-core machines. > Can you please suggest me some papers or study material that can explain > communication models that incorporate network communication as well as > shared memory communication. > > Thanks, > Ansar >

1 0

Message Passing models for Hybrid Parallelism
by Muhammad Ansar Javed 28 Aug '13

28 Aug '13

Hi, I am looking for message passing models for Hybrid Parallelism that are being used in MPICH implementations for the Cluster of Multi-core machines. Can you please suggest me some papers or study material that can explain communication models that incorporate network communication as well as shared memory communication. Thanks, Ansar

1 0

Re: [mpich-devel] MPI_Errhandler Documentation
by Jim Dinan 21 Aug '13

21 Aug '13

Also, in the MPICH manpages. ~Jim. On Wed, Aug 21, 2013 at 11:49 AM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > Maybe in the user guide (doc/userguide) > > Rajeev > > On Aug 20, 2013, at 9:04 AM, Wesley Bland wrote: > > > In some of my work, I came upon this passage in the standard describing > how to create a custom MPI_Errhandler: > > > > The user routine should be, in C, a function of type > MPI_Comm_errhandler_function, which is defined as > > > > typedef void MPI_Comm_errhandler_function(MPI_Comm *, int *, ...); > > > > The first argument is the communicator in use. The second is the error > code to be returned by the MPI routine that raised the error. If the > routine would have returned MPI_ERR_IN_STATUS, it is the error code > returned in the status for the request that caused the error handler to be > invoked. The remaining arguments are “varargs” arguments whose number and > meaning is implementation-dependent. An implementation should clearly doc- > ument these arguments. > > > > The last sentence is bolded because AFAICT, we haven't documented this > anywhere. Digging through the code, it looks like we don't provide any > extra arguments so the function is just: > > > > void MPI_Comm_errhandler_function(MPI_Comm *, int *); > > > > I'm happy to write this, but does anyone have a suggestion where the > best place to document this would be? > > > > Thanks, > > Wesley > >

1 0

Re: [mpich-devel] MPI_Errhandler Documentation
by Rajeev Thakur 21 Aug '13

21 Aug '13

Maybe in the user guide (doc/userguide) Rajeev On Aug 20, 2013, at 9:04 AM, Wesley Bland wrote: > In some of my work, I came upon this passage in the standard describing how to create a custom MPI_Errhandler: > > The user routine should be, in C, a function of type MPI_Comm_errhandler_function, which is defined as > > typedef void MPI_Comm_errhandler_function(MPI_Comm *, int *, ...); > > The first argument is the communicator in use. The second is the error code to be returned by the MPI routine that raised the error. If the routine would have returned MPI_ERR_IN_STATUS, it is the error code returned in the status for the request that caused the error handler to be invoked. The remaining arguments are “varargs” arguments whose number and meaning is implementation-dependent. An implementation should clearly doc- ument these arguments. > > The last sentence is bolded because AFAICT, we haven't documented this anywhere. Digging through the code, it looks like we don't provide any extra arguments so the function is just: > > void MPI_Comm_errhandler_function(MPI_Comm *, int *); > > I'm happy to write this, but does anyone have a suggestion where the best place to document this would be? > > Thanks, > Wesley

1 0

MPI_Errhandler Documentation
by Wesley Bland 20 Aug '13

20 Aug '13

In some of my work, I came upon this passage in the standard describing how to create a custom MPI_Errhandler: The user routine should be, in C, a function of type MPI_Comm_errhandler_function, which is defined as typedef void MPI_Comm_errhandler_function(MPI_Comm *, int *, ...); The first argument is the communicator in use. The second is the error code to be returned by the MPI routine that raised the error. If the routine would have returned MPI_ERR_IN_STATUS, it is the error code returned in the status for the request that caused the error handler to be invoked. The remaining arguments are “varargs” arguments whose number and meaning is implementation-dependent. An implementation should clearly doc- ument these arguments. The last sentence is bolded because AFAICT, we haven't documented this anywhere. Digging through the code, it looks like we don't provide any extra arguments so the function is just: void MPI_Comm_errhandler_function(MPI_Comm *, int *); I'm happy to write this, but does anyone have a suggestion where the best place to document this would be? Thanks, Wesley

1 0

RMA testing problems
by Jeff Hammond 19 Aug '13

19 Aug '13

I'm seeing 26 of 107 RMA tests fail on my Mac (see attached). I have partially resolved the previously reported errors using dynamic linking. This is with an unmodified clone of origin ("git reset --hard origin/master"). Should I assume I'm just cursed and ignore these errors? I can't reproduce them on a totally different platform, but that is not really any consolation. If this Mac crap doesn't stop, I guess I'll have to live in my Debian VM for MPI development from now on... Thanks, Jeff -- Jeff Hammond jeff.science(a)gmail.com

1 0

Re: [mpich-devel] hwloc build failing on Mac with GCC
by Jeff Hammond 01 Aug '13

01 Aug '13

I didn't ./autogen.sh after my git update. Maybe that's the issue. Anyways, I'm doing that now and then following Dave's instructions. Jeff ----- Original Message ----- > From: "David Goodell (dgoodell)" <dgoodell(a)cisco.com> > To: "<devel(a)mpich.org>" <devel(a)mpich.org> > Cc: "Jeff Hammond" <jhammond(a)alcf.anl.gov> > Sent: Thursday, August 1, 2013 8:57:44 AM > Subject: Re: [mpich-devel] hwloc build failing on Mac with GCC > > From the error message, this is the sort of thing that usually shows > up when "-arch x86_64" and "-arch i386" flags get dropped or > mismatched somewhere in configure. Sometimes it's an "-m32"/"-m64" > issue instead. > > ----8<---- > CCLD hydra_persist > ld: warning: ignoring file > /Users/jhammond/eclipse/MPICH2/git/build-gcc/src/pm/hydra/tools/topo/hwloc/hwloc/src/.libs/libhwloc_embedded.a, > file was built for archive which is not the architecture being > linked (x86_64): > /Users/jhammond/eclipse/MPICH2/git/build-gcc/src/pm/hydra/tools/topo/hwloc/hwloc/src/.libs/libhwloc_embedded.a > Undefined symbols for architecture x86_64: > ----8<---- > > One source of such a mismatch for me in the past has been differing > 32/64 defaults between my C compiler and my Fortran compiler, though > that doesn't seem likely in this case because: > > 1) all of your compilers are from MacPorts and presumably should have > the same default; > > 2) this is an hydra/hwloc build error, so Fortran probably isn't > entering into this. > > "make clean", rebuild with V=1, and check for compiler argument > mismatch between the hwloc files and the hydra files. > > -Dave > > On Aug 1, 2013, at 8:28 AM, Wesley Bland <wbland(a)mcs.anl.gov> wrote: > > > I used the exact same setup without an issue. I'm not sure what's > > going on. > > > > On August 1, 2013 at 8:22:03 AM, Wesley Bland (wbland(a)mcs.anl.gov) > > wrote: > > > >> 10.7.4 is the OS version, not the kernel version. I'm building on > >> my laptop on the same version as you without any issues. I've > >> been using GCC as well, but I'll try your exact config to see if > >> something different happens for me. > >> > >> Wesley > >> > >> On July 31, 2013 at 6:33:34 PM, Jeff Hammond > >> (jhammond(a)alcf.anl.gov) wrote: > >> > >>> How different is 11.4.2 from 10.7.4? Seems like a big diff in the > >>> OS dimension. > >>> > >>> I'd really like to try to narrow this down because I'm currently > >>> blocked on this w.r.t. an app I'm trying to run. > >>> > >>> Jeff > >>> > >>> ----- Original Message ----- > >>> > From: "Ken Raffenetti" <raffenet(a)mcs.anl.gov> > >>> > To: devel(a)mpich.org > >>> > Sent: Wednesday, July 31, 2013 5:40:55 PM > >>> > Subject: Re: [mpich-devel] hwloc build failing on Mac with GCC > >>> > > >>> > I'll just note that building on our OSX 10.7.4 test environment > >>> > doesn't show any issues in this configuration. > >>> > > >>> > ----- Original Message ----- > >>> > > From: "Jeff Hammond" <jhammond(a)alcf.anl.gov> > >>> > > To: devel(a)mpich.org > >>> > > Sent: Wednesday, July 31, 2013 4:00:59 PM > >>> > > Subject: Re: [mpich-devel] hwloc build failing on Mac with > >>> > > GCC > >>> > > > >>> > > Yes, that's right. Sorry. It's attached. > >>> > > > >>> > > Jeff > >>> > > > >>> > > ----- Original Message ----- > >>> > > > From: "Ken Raffenetti" <raffenet(a)mcs.anl.gov> > >>> > > > To: devel(a)mpich.org > >>> > > > Sent: Wednesday, July 31, 2013 3:51:01 PM > >>> > > > Subject: Re: [mpich-devel] hwloc build failing on Mac with > >>> > > > GCC > >>> > > > > >>> > > > Maybe I'm missing something, but I fail to find a problem > >>> > > > in the > >>> > > > attachment. Did you mean to attach a make log? > >>> > > > > >>> > > > ----- Original Message ----- > >>> > > > > From: "Jeff Hammond" <jhammond(a)alcf.anl.gov> > >>> > > > > To: "MPICH" <devel(a)mpich.org> > >>> > > > > Sent: Wednesday, July 31, 2013 2:43:55 PM > >>> > > > > Subject: [mpich-devel] hwloc build failing on Mac with > >>> > > > > GCC > >>> > > > > > >>> > > > > Am I stupid or is something broken? This is the git head > >>> > > > > as of > >>> > > > > a > >>> > > > > few > >>> > > > > minutes ago. > >>> > > > > > >>> > > > > Note that the essence of the problem is in the > >>> > > > > attachment. I > >>> > > > > will > >>> > > > > not > >>> > > > > repeat it here. > >>> > > > > > >>> > > > > Thanks, > >>> > > > > > >>> > > > > Jeff > >>> > > > > > >>> > > > > Jeffs-MacBook-Pro:build-gcc jhammond$ gcc -v > >>> > > > > Using built-in specs. > >>> > > > > COLLECT_GCC=gcc > >>> > > > > COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin11/4.8.1/lto-wrapper > >>> > > > > Target: x86_64-apple-darwin11 > >>> > > > > Configured with: ../gcc-4.8.1/configure > >>> > > > > --prefix=/opt/local > >>> > > > > --build=x86_64-apple-darwin11 > >>> > > > > --enable-languages=c,c++,objc,obj-c++,lto,fortran,java > >>> > > > > --libdir=/opt/local/lib/gcc48 > >>> > > > > --includedir=/opt/local/include/gcc48 > >>> > > > > --infodir=/opt/local/share/info > >>> > > > > --mandir=/opt/local/share/man > >>> > > > > --datarootdir=/opt/local/share/gcc-4.8 > >>> > > > > --with-local-prefix=/opt/local > >>> > > > > --with-system-zlib --disable-nls --program-suffix=-mp-4.8 > >>> > > > > --with-gxx-include-dir=/opt/local/include/gcc48/c++/ > >>> > > > > --with-gmp=/opt/local --with-mpfr=/opt/local > >>> > > > > --with-mpc=/opt/local > >>> > > > > --with-ppl=/opt/local --with-cloog=/opt/local > >>> > > > > --enable-cloog-backend=isl --disable-cloog-version-check > >>> > > > > --enable-stage1-checking --disable-multilib --enable-lto > >>> > > > > --enable-libstdcxx-time --with-as=/opt/local/bin/as > >>> > > > > --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar > >>> > > > > --with-bugurl=https://trac.macports.org/newticket > >>> > > > > --with-pkgversion='MacPorts gcc48 4.8.1_1' > >>> > > > > Thread model: posix > >>> > > > > gcc version 4.8.1 (MacPorts gcc48 4.8.1_1) > >>> > > > > Jeffs-MacBook-Pro:build-gcc jhammond$ g++ -v > >>> > > > > Using built-in specs. > >>> > > > > COLLECT_GCC=g++ > >>> > > > > COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin11/4.8.1/lto-wrapper > >>> > > > > Target: x86_64-apple-darwin11 > >>> > > > > Configured with: ../gcc-4.8.1/configure > >>> > > > > --prefix=/opt/local > >>> > > > > --build=x86_64-apple-darwin11 > >>> > > > > --enable-languages=c,c++,objc,obj-c++,lto,fortran,java > >>> > > > > --libdir=/opt/local/lib/gcc48 > >>> > > > > --includedir=/opt/local/include/gcc48 > >>> > > > > --infodir=/opt/local/share/info > >>> > > > > --mandir=/opt/local/share/man > >>> > > > > --datarootdir=/opt/local/share/gcc-4.8 > >>> > > > > --with-local-prefix=/opt/local > >>> > > > > --with-system-zlib --disable-nls --program-suffix=-mp-4.8 > >>> > > > > --with-gxx-include-dir=/opt/local/include/gcc48/c++/ > >>> > > > > --with-gmp=/opt/local --with-mpfr=/opt/local > >>> > > > > --with-mpc=/opt/local > >>> > > > > --with-ppl=/opt/local --with-cloog=/opt/local > >>> > > > > --enable-cloog-backend=isl --disable-cloog-version-check > >>> > > > > --enable-stage1-checking --disable-multilib --enable-lto > >>> > > > > --enable-libstdcxx-time --with-as=/opt/local/bin/as > >>> > > > > --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar > >>> > > > > --with-bugurl=https://trac.macports.org/newticket > >>> > > > > --with-pkgversion='MacPorts gcc48 4.8.1_1' > >>> > > > > Thread model: posix > >>> > > > > gcc version 4.8.1 (MacPorts gcc48 4.8.1_1) > >>> > > > > Jeffs-MacBook-Pro:build-gcc jhammond$ gfortran -v > >>> > > > > Using built-in specs. > >>> > > > > COLLECT_GCC=gfortran > >>> > > > > COLLECT_LTO_WRAPPER=/opt/local/libexec/gcc/x86_64-apple-darwin11/4.8.1/lto-wrapper > >>> > > > > Target: x86_64-apple-darwin11 > >>> > > > > Configured with: ../gcc-4.8.1/configure > >>> > > > > --prefix=/opt/local > >>> > > > > --build=x86_64-apple-darwin11 > >>> > > > > --enable-languages=c,c++,objc,obj-c++,lto,fortran,java > >>> > > > > --libdir=/opt/local/lib/gcc48 > >>> > > > > --includedir=/opt/local/include/gcc48 > >>> > > > > --infodir=/opt/local/share/info > >>> > > > > --mandir=/opt/local/share/man > >>> > > > > --datarootdir=/opt/local/share/gcc-4.8 > >>> > > > > --with-local-prefix=/opt/local > >>> > > > > --with-system-zlib --disable-nls --program-suffix=-mp-4.8 > >>> > > > > --with-gxx-include-dir=/opt/local/include/gcc48/c++/ > >>> > > > > --with-gmp=/opt/local --with-mpfr=/opt/local > >>> > > > > --with-mpc=/opt/local > >>> > > > > --with-ppl=/opt/local --with-cloog=/opt/local > >>> > > > > --enable-cloog-backend=isl --disable-cloog-version-check > >>> > > > > --enable-stage1-checking --disable-multilib --enable-lto > >>> > > > > --enable-libstdcxx-time --with-as=/opt/local/bin/as > >>> > > > > --with-ld=/opt/local/bin/ld --with-ar=/opt/local/bin/ar > >>> > > > > --with-bugurl=https://trac.macports.org/newticket > >>> > > > > --with-pkgversion='MacPorts gcc48 4.8.1_1' > >>> > > > > Thread model: posix > >>> > > > > gcc version 4.8.1 (MacPorts gcc48 4.8.1_1) > >>> > > > > Jeffs-MacBook-Pro:build-gcc jhammond$ uname -a > >>> > > > > Darwin Jeffs-MacBook-Pro.local 11.4.2 Darwin Kernel > >>> > > > > Version > >>> > > > > 11.4.2: > >>> > > > > Thu Aug 23 16:25:48 PDT 2012; > >>> > > > > root:xnu-1699.32.7~1/RELEASE_X86_64 > >>> > > > > x86_64 > >>> > > > > > >>> > > > > -- > >>> > > > > Jeff Hammond > >>> > > > > Argonne Leadership Computing Facility > >>> > > > > University of Chicago Computation Institute > >>> > > > > jhammond(a)alcf.anl.gov / (630) 252-5381 > >>> > > > > http://www.linkedin.com/in/jeffhammond > >>> > > > > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > >>> > > > > ALCF docs: http://www.alcf.anl.gov/user-guides > >>> > > > > > >>> > > > > >>> > > > >>> > > -- > >>> > > Jeff Hammond > >>> > > Argonne Leadership Computing Facility > >>> > > University of Chicago Computation Institute > >>> > > jhammond(a)alcf.anl.gov / (630) 252-5381 > >>> > > http://www.linkedin.com/in/jeffhammond > >>> > > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > >>> > > ALCF docs: http://www.alcf.anl.gov/user-guides > >>> > > > >>> > > > >>> > > >>> > >>> -- > >>> Jeff Hammond > >>> Argonne Leadership Computing Facility > >>> University of Chicago Computation Institute > >>> jhammond(a)alcf.anl.gov / (630) 252-5381 > >>> http://www.linkedin.com/in/jeffhammond > >>> https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > >>> ALCF docs: http://www.alcf.anl.gov/user-guides > >> > >> > > > > > > -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides

1 0