August 2015 - discuss - mailman3.cels.anl.gov

Argonne Spam Quarantine Notification
by Argonne Anti Spam Quarantine 28 Aug '15

28 Aug '15

++ Note: This message has been sent by a notification only system. Please do not reply ++ IronPort Spam Quarantine Notification If a spam message was missed, or if a message was incorrectly flagged as spam, you can add the sender to a personal safelist or blocklist via the quarantine. Senders on the safelist will not be flagged as spam, and senders on the blocklist will be automatically quarantined. For more information, visit: https://wiki.inside.anl.gov/inside/Ironport_Anti-Spam_Appliances/Documentat… The message(s) below have been quarantined by the Argonne National Laboratory spam filtering system. There are 1 new messages in your Email Quarantine since you received your last Spam Quarantine Notification. If the messages below are spam, you do not need to take any action. Messages will be automatically deleted from the quarantine after 28 day(s). If any of the messages below are not spam, click the 'Release' link to have them sent to your Inbox. Messages that have been correctly flagged as spam do not need to be reported. ----------- New Quarantine Messages --------------- Message 1 From: Google Corporations® <enriquegu(a)municipiojipijapa.gob.ec> Subject: Google Notification Award Date: 27 Aug 2015 Release: http://mailgateway.anl.gov:8080/Message?action=Release&mid=91713358&h=c4d2a… --------------------------------------------------- To manage your quarantine please visit the URL below: http://mailgateway.anl.gov:8080/Search?h=21f1498397973e308911f990a5530a1b&e… If you have any questions regarding the Laboratory spam filtering product, please contact the CIS helpdesk at help(a)anl.gov or x-9999 option 2.

1 0

Re: [mpich-discuss] mpich issues when configuring
by Jie Ren 26 Aug '15

26 Aug '15

Hi Ken, Problem solved, the issue was I defined the name of folder with space which should not be included in. After deleting them, configuration worked out eventually. Thanks, Jie On Wed, Aug 26, 2015 at 1:03 PM, Kenneth Raffenetti <raffenet(a)mcs.anl.gov> wrote: > Did you add just CC=gcc? If so, configure will still detect and prefer the > Intel C++ and Fortran compilers if they are present in your path. The > license problem will remain. > > Ken > > On 08/21/2015 11:37 AM, Jie Ren wrote: > >> Hi Ken, >> >> Thanks for your suggestion, I did try adding CC=gcc, however it keeps >> giving me the same errors. >> >> Thanks, >> >> Jie >> >> On Fri, Aug 21, 2015 at 1:08 PM, Kenneth Raffenetti >> <raffenet(a)mcs.anl.gov <mailto:[email protected]>> wrote: >> >> It appears that the configure script is discovering a version of icc >> in your path, but it is unable to compile with it. Your system may >> not be configured to use it. I would suggest trying different >> compilers if you have them available. I.e. add "CC=gcc CXX=g++ >> FC=gfortran" to your configure line. >> >> Ken >> >> >> On 08/21/2015 12:37 PM, Jie Ren wrote: >> >> I met a problem when I was configuring the mpich on my linux >> machine as >> below. I also attached the package of c.txt, config.log(the main >> one, >> openpa one and mpl one, looks like I don't have the other two >> config.log >> files when I got the errors). >> >> Thanks, >> >> Jie >> >> configure: error: in `/data/Research/Task 17 SU2 >> Study/mpich-3.1.1/src/openpa': >> configure: error: C compiler cannot create executables >> See `config.log' for more details >> configure: error: OpenPA configure failed >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> >> _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] mpich issues when configuring
by Kenneth Raffenetti 26 Aug '15

26 Aug '15

Did you add just CC=gcc? If so, configure will still detect and prefer the Intel C++ and Fortran compilers if they are present in your path. The license problem will remain. Ken On 08/21/2015 11:37 AM, Jie Ren wrote: > Hi Ken, > > Thanks for your suggestion, I did try adding CC=gcc, however it keeps > giving me the same errors. > > Thanks, > > Jie > > On Fri, Aug 21, 2015 at 1:08 PM, Kenneth Raffenetti > <raffenet(a)mcs.anl.gov <mailto:[email protected]>> wrote: > > It appears that the configure script is discovering a version of icc > in your path, but it is unable to compile with it. Your system may > not be configured to use it. I would suggest trying different > compilers if you have them available. I.e. add "CC=gcc CXX=g++ > FC=gfortran" to your configure line. > > Ken > > > On 08/21/2015 12:37 PM, Jie Ren wrote: > > I met a problem when I was configuring the mpich on my linux > machine as > below. I also attached the package of c.txt, config.log(the main > one, > openpa one and mpl one, looks like I don't have the other two > config.log > files when I got the errors). > > Thanks, > > Jie > > configure: error: in `/data/Research/Task 17 SU2 > Study/mpich-3.1.1/src/openpa': > configure: error: C compiler cannot create executables > See `config.log' for more details > configure: error: OpenPA configure failed > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

EuroMPI 2015 Call for Participation - Early deadline Sept 1st
by Brice Goglin 26 Aug '15

26 Aug '15

EuroMPI 2015 Call for participation EuroMPI 2015 in-cooperation status with ACM and SIGHPC in Bordeaux France, 21st - 23rd September, 2015. The prime annual meeting for researchers, developers, and students in message-passing parallel computing with MPI and related paradigms. **** Deadline of early registration is Sept 1st, 2015 ***** https://eurompi2015.bordeaux.inria.fr/ The conference will feature 14 strong technical paper presentations, 3 invited talks, 3 tutorials and posters. The list of accepted papers is attached in this CFP. The detailed conference information is being incrementally updated at https://eurompi2015.bordeaux.inria.fr/ Please watch the URL to get the latest information. TUTORIALS ------------------------------- - Performance analysis for High Performance Systems, François Trahay, Telecom SudParis - Understanding and managing hardware affinities with Hardware Locality (hwloc) Brice Goglin, INRIA Bordeaux sud-Ouest - Insightful Automatic Performance Modeling Alexandru Calotoiu, TU Darmstadt INVITED TALKS ------------------------------- - A new high performance network for HPC systems: Bull eXascale Interconnect (BXI), Jean-Pierre Panziera, Chief Technology Director for Extreme Computing at Atos - Computational Fluid Dynamics and High performance computing, Gabriel Staffelbach, Senior Researcher at CERFACS - Is your software ready for exascale? – How the next generation of performance tools can give you the answer. Prof. Felix Wolf, Department of Computer Science of TU Darmstadt IMPORTANT DATES ------------------------------- - Early Registration Deadline: September 1st, 2015 - Tutorials: September 21st, 2015 - Conference: September 22nd-23rd, 2015 ACCEPTED PAPERS ------------------------------- -"A Memory Management System Optimized for BDMPI's Memory and Execution Model", Jeremy Iverson and George Karypis -"An MPI Halo-Cell Implementation for Zero-Copy Abstraction", Jean-Baptiste Besnard, Allen Malony, Sameer Shende, Marc Pérache, Patrick Carribault and Julien Jaeger -"DAME: A Runtime-Compiled Engine for Derived Datatypes",Tarun Prabhu and William Gropp -"Detecting Silent Data Corruption for Extreme-Scale MPI Applications", Leonardo Arturo Bautista Gomez and Franck Cappello -"Efficient MPI Datatype Reconstruction for Vector and Index Types", Martin Kalany and Jesper Larsson Träff -"GPU-Aware Design, Implementation, and Evaluation of Non-blocking Collective Benchmarks", Ammar Ahmad Awan, Hari Subramoni, Khaled Hamidouche, Akshay Venkatesh, Jonathan Perkins and Dhabaleswar K. Panda -"Isomorphic, Sparse MPI-like Collective Communication Operations for Parallel Stencil Computations", Jesper Larsson Träff, Felix Lübbe, Antoine Rougier and Sascha Hunold -"MPI Advisor: a Minimal Overhead MPI Performance Tuning Tool", Esthela Gallardo, Jerome Vienne, Leonardo Fialho, Patricia Teller and James Browne -"MPI-focused Tracing with OTFX: An MPI-aware In-memory Event Tracing Extension to the Open Trace Format 2", Michael Wagner, Jens Doleschal and Andreas Knüpfer -"On the Impact of Synchronizing Clocks and Processes on Benchmarking MPI Collectives", Sascha Hunold and Alexandra Carpen-Amarie -"Plan B: Interruption of Ongoing MPI Operations to Support Failure Recovery", "Aurelien Bouteiller, George Bosilca and Jack Dongarra -"Scalable and Fault Tolerant Failure Detection and Consensus", Amogh Katti, Giuseppe Di Fatta, Thomas Naughton and Christian Engelmann -"Sliding Substitution of Failed Nodes", Atsushi Hori, Kazumi Yoshinaga, Thomas Hérault, Aurélien Bouteiller and George Bosilca and Yutaka Ishikawa -"Toward Operating System Support for Scalable Multithreaded Message Passing", Balazs Gerofi, Masamichi Takagi and Yutaka Ishikawa _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

(no subject)
by surrienn ddraah 26 Aug '15

26 Aug '15

Hello After submitting on tyrone cluster, Graph500 application with Jumpshot profiler it is generating the following error. in BFS level-3 ----------------------------- ----------------------------------------------- clog_preamble.c:CLOG_Preamble_write() - Error Write to the logfile fails. ----------------------------------------------------------------------------- Any idea how to resolve this error _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] mpich issues when configuring
by Jie Ren 21 Aug '15

21 Aug '15

Hi Ken, Thanks for your suggestion, I did try adding CC=gcc, however it keeps giving me the same errors. Thanks, Jie On Fri, Aug 21, 2015 at 1:08 PM, Kenneth Raffenetti <raffenet(a)mcs.anl.gov> wrote: > It appears that the configure script is discovering a version of icc in > your path, but it is unable to compile with it. Your system may not be > configured to use it. I would suggest trying different compilers if you > have them available. I.e. add "CC=gcc CXX=g++ FC=gfortran" to your > configure line. > > Ken > > > On 08/21/2015 12:37 PM, Jie Ren wrote: > >> I met a problem when I was configuring the mpich on my linux machine as >> below. I also attached the package of c.txt, config.log(the main one, >> openpa one and mpl one, looks like I don't have the other two config.log >> files when I got the errors). >> >> Thanks, >> >> Jie >> >> configure: error: in `/data/Research/Task 17 SU2 >> Study/mpich-3.1.1/src/openpa': >> configure: error: C compiler cannot create executables >> See `config.log' for more details >> configure: error: OpenPA configure failed >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> >> _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] mpich issues when configuring
by Kenneth Raffenetti 21 Aug '15

21 Aug '15

It appears that the configure script is discovering a version of icc in your path, but it is unable to compile with it. Your system may not be configured to use it. I would suggest trying different compilers if you have them available. I.e. add "CC=gcc CXX=g++ FC=gfortran" to your configure line. Ken On 08/21/2015 12:37 PM, Jie Ren wrote: > I met a problem when I was configuring the mpich on my linux machine as > below. I also attached the package of c.txt, config.log(the main one, > openpa one and mpl one, looks like I don't have the other two config.log > files when I got the errors). > > Thanks, > > Jie > > configure: error: in `/data/Research/Task 17 SU2 > Study/mpich-3.1.1/src/openpa': > configure: error: C compiler cannot create executables > See `config.log' for more details > configure: error: OpenPA configure failed > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Mac OS X version of Mpich
by Benjamin Svetitsky 21 Aug '15

21 Aug '15

_______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

mpich issues when configuring
by Jie Ren 21 Aug '15

21 Aug '15

I met a problem when I was configuring the mpich on my linux machine as below. I also attached the package of c.txt, config.log(the main one, openpa one and mpl one, looks like I don't have the other two config.log files when I got the errors). Thanks, Jie configure: error: in `/data/Research/Task 17 SU2 Study/mpich-3.1.1/src/openpa': configure: error: C compiler cannot create executables See `config.log' for more details configure: error: OpenPA configure failed _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Mac OS X version of Mpich
by Jeff Hammond 19 Aug '15

19 Aug '15

On Wed, Aug 19, 2015 at 11:24 AM, Dave Goodell (dgoodell) < dgoodell(a)cisco.com> wrote: > On Aug 19, 2015, at 6:29 AM, Jeff Hammond <jeff.science(a)gmail.com> wrote: > > > See below where you got a warning for defining MPI to 1? That is going > to break EVERYTHING in the MPI C code. Consider the declaration > MPI_Init_thread. It will become 1_Init_thread. This is a serious problem. > > This isn't how the C preprocessor works, Jeff... "#define f x" will not > change "fprintf" to "xprintf" later in the source file. > > <facepalm> I offer as a pathetic excuse my lack of caffeination when I wrote that nonsensical statement. Jeff > > The MPI standard reserves the MPI namespace. You cannot use it. In > your case, you took the entire namespace and changed it to a number :-) > > > > Please use a preprocessor macro like USE_MPI in your application. Do > not define any symbols anywhere that being with MPI. > > This, however, is good advice and should fix this particular issue. > > -Dave > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0