April 2009 - Mpich2-core - mailman3.cels.anl.gov

The *right* way to decl/define conditionally used variables
by Jayesh Krishna 30 Apr '09

30 Apr '09

Hi, In the current code base we have functions to declare variables used within MPIU_Assert() statements. These functions use compiler attributes to declare the variables as "unused". In the case of the compilers like Visual Studio (there could be more) which don't support these "unused" compiler attributes we get warnings about "declared but unused" variables. One possibility is to separate the definition and declaration of the variables and trick compilers that don't support "unused" attributes (like VS) to *think*ing that these variables are used. ======================== current code base ================================= #if (!defined(NDEBUG) && defined(HAVE_ERROR_CHECKING)) ... #else # define MPIU_Assert(a_) /* Empty decls not allowed in C */ # define MPIU_AssertDecl(a_) a_ # define MPIU_AssertDeclValue(_a,_b) _a ATTRIBUTE((unused)) #endif ======================== current code base ================================= ======================== suggestion ================================= #if (!defined(NDEBUG) && defined(HAVE_ERROR_CHECKING)) ... #else # define MPIU_Assert(a_) /* Empty decls not allowed in C */ # define MPIU_AssertDecl(a_) a_ ATTRIBUTE((unused)) # define MPIU_AssertVarAssign(_a, _b) \ # ifdef HAVE_WINDOWS_H \ _a \ # endif /* REMOVE *DeclValue() */ /* # define MPIU_AssertDeclValue(_a,_b) _a ATTRIBUTE((unused)) */ #endif ======================== suggestion ================================= What does everyone think (Is there a better way ?) ? Regards, Jayesh

3 11

[Fwd: [mcs-systems #28024] old web pages]
by Darius Buntinas 23 Apr '09

23 Apr '09

Here are the old web pages. -d -------- Original Message -------- Subject: [mcs-systems #28024] old web pages Date: Wed, 22 Apr 2009 11:25:22 -0500 From: Ken Raffenetti <raffenet(a)mcs.anl.gov> Reply-To: systems(a)mcs.anl.gov, Ken Raffenetti <raffenet(a)mcs.anl.gov> To: buntinas(a)mcs.anl.gov CC: leggett(a)mcs.anl.gov References: <RT-Ticket-28024(a)mcs.anl.gov> <49ECBFA7.9090505(a)mcs.anl.gov> Darius, You can find the old files at /mcs/www/mpi/ Ken On Mon Apr 20 13:32:14 2009, buntinas wrote: > > Hi, > > Are the old web pages still available somewhere (even through nfs)? > Specifically, I'm looking for this page: > > http://www-unix.mcs.anl.gov/mpi/mpichold/developer/design/pmiv2.htm > > Thanks! > > -d

1 0

Fwd: btlaunchmany on bblogin
by Anthony Chan 10 Apr '09

10 Apr '09

Do nightlies allocate nodes repeatedly ? If so, when do nightlies run so I can schedule my use of breadboard around it ? A.Chan ----- "Narayan Desai" <desai(a)mcs.anl.gov> wrote: > On Fri, 10 Apr 2009 16:16:05 -0500 (CDT) Anthony Chan wrote: > > > Anthony> Can bballoc run for few hours ? of the order of 4 hours. > > Whenever a user allocates a node, it causes load on both btlaunchmany > and nfs. If users are allocating and deallocating nodes frequently, > it > can do this. If there were a script that were doing it, this sort of > thing could last quite some time. > -nld

2 3

btlaunchmany on bblogin
by Anthony Chan 10 Apr '09

10 Apr '09

I have been using breadboard late into the night in last few days, I notice that whenever btlanunchmany is run (by root) the NFS becomes very so slow on bblogin as well as other bbXX nodes that many 1-second test becomes stuck, essentially the whole cluster becomes very slow. Wonder if anyone knows if btlanchmany is a legit service that should be run by root ? Google search shows that btlaunchmany is some kind bit torrent service... A.Chan

2 4

Fwd: CFP (extended deadline): 25th IEEE International Conference on Software Maintenance
by Rusty Lusk 02 Apr '09

02 Apr '09

Anyone interested in this? Begin forwarded message: > From: icsm-info(a)FernUni-Hagen.de > Date: April 1, 2009 12:46:32 PM CDT > To: icsm-info(a)FernUni-Hagen.de > Subject: CFP (extended deadline): 25th IEEE International Conference > on Software Maintenance > > CALL FOR PAPERS - (the submission deadline has been extended until > April 10) > > > 25th IEEE International Conference on Software Maintenance > > ICSM 2009 > Edmonton, Canada -- September 20-26, 2009 > > http://icsm2009.cs.ualberta.ca/ > > Sponsored by IEEE Computer Society > ------------------------------------------------------------ > DATES (*updated*) > > April 3, 2009 Research abstracts due > April 10, 2009 Research papers due > May 1, 2009 All other track submissions due > May 29, 2009 Notifications sent to authors > ------------------------------------------------------------ > > ICSM is the premier international event in the software > maintenance field for participants from academia, > government, and industry to share ideas and experiences for > solving critical software maintenance problems. > > The 25th International Conference on Software Maintenance > (ICSM 2009) will be held in Edmonton, Alberta, Canada, one > of the most vibrant cities in Canada bordering the beautiful > Canadian Rockies. > > We invite high-quality English-language submissions to all > conference tracks. Submissions must be PDF files following > the two-column IEEE CS proceedings style. Please check the > conference web sites for further information. > > Please forward this call to anyone who may be interested. > > http://icsm2009.cs.ualberta.ca/ > ------------------------------------------------------------ > RESEARCH PAPERS > > Research papers should describe original and significant > work in the research and practice of software maintenance > and evolution. Case studies, empirical research, and > experiments are particularly welcome. We also welcome > papers that present leading-edge ideas in maintenance. > Papers must not have been previously accepted for > publication nor concurrently submitted for review in > another journal, book, or conference. > Page limit: 10 > Due: April 3, 2009 (Abstracts) -- April 10, 2009 (Papers) > > Topics of interest include but are not limited to: > > * Experience reports > * Techniques, methods and processes: > o to facilitate and support software maintenance > o to analyze and comprehend software systems > o to specify, design, implement and test evolvable systems > * Maintenance and evolution of multi-language, multi-platform, > and network-centric systems > * Model driven software maintenance and evolution > ------------------------------------------------------------ > WORKSHOPS AND PANELS > > We invite proposals for workshops and panels on any topic > related to software maintenance. Workshop and panel sessions > are to be designed around a specific theme and be > interactive and discussion oriented. > > Page limit: 2. > Due: April 24, 2009 > ------------------------------------------------------------ > DOCTORAL SYMPOSIUM > > We welcome submissions from young researchers who are > currently working on or who have delivered their Ph.D. > dissertation in the software maintenance and evolution area > within the last two years. > > Page limit: 4. > Due: May 1, 2009 > ------------------------------------------------------------ > INDUSTRY TRACK > > This track invites proposals for presentations of industrial > applications and practices. These proposals can include > state-of-the-art descriptions, state-of-the-practice > reports, and survey papers from real-world projects and > industrial experiences. > > Page limit: 4. > Due: May 1, 2009 > ------------------------------------------------------------ > TOOL DEMONSTRATIONS > > We invite proposals for tool demonstrations on any topic > related to software maintenance and evolution. > Demonstrations will be in an open session to allow > individual interaction with the participants. > > Page limit: 2. > Due: May 1, 2009 > ------------------------------------------------------------ > CO-LOCATED EVENTS > > ICSM 2009 is co-located with: > > SCAM 2009: > The 9th IEEE International Working Conference > on Source Code Analysis and Manipulation > September 20-21 > http://www2009.ieee-scam.org/ > > WSE 2009: > The 11th IEEE International Symposium > on Web Systems Evolution > September 25-26 > http://www.sei.buaa.edu.cn/wse09/ > > VISSOFT 2009: > The 5th IEEE International Workshop > on Visualizing Software for Understanding and Analysis > September 25-26 > ------------------------------------------------------------ > GENERAL CHAIR > > Eleni Stroulia, University of Alberta > > PROGRAM CHAIRS > > Kostas Kontogiannis, National Technical U Athens > Tao Xie, NC State University > > http://icsm2009.cs.ualberta.ca/conf.php > > > > > > > > > > > > > _______________________________________________ > icsm-info mailing list > icsm-info(a)fernuni-hagen.de > http://www.fernuni-hagen.de/mailman/listinfo/icsm-info

1 0

Re: [mpich2-core] Fwd: [mpich2-maint] #509: Cannot build mpich2-1.0.8p1 (nemesis) with PGI 8.0-4 on Linux x86_64
by Anthony Chan 01 Apr '09

01 Apr '09

The simplest thing to do is add a line "+pgi" to your $HOME/.soft. and then logout/login. That has the advantage that everything got setup correctly including MANPATH (It took few emails with rick to get this corrected) If you want to do it yourself, add these env variables: PGI=/soft/com/packages/pgi-7.1-6 LD_LIBRARY_PATH=....:/soft/com/packages/pgi-7.1-6/linux86-64/7.1-6/lib MANPATH=....:/soft/com/packages/pgi-7.1-6/linux86-64/7.1-6/man:: PATH=....:/soft/com/packages/pgi-7.1-6/linux86-64/7.1-6/bin A.Chan ----- "Dave Goodell" <goodell(a)mcs.anl.gov> wrote: > Anthony, do you know how to set the right license environment > variables for our PGI installation? > > -Dave > > octagon% cat foo.c > > int main(int argc, char **argv) > { > return 0; > } > > octagon% pgcc foo.c > Your PGI license doesn't appear to be working properly. > > 1. If you installed a trial version, please generate and then > install > your trial keys at: > > http://www.pgroup.com/license/trial > > To generate your trial keys, you will need your host ID. > > Your hostid is 00304857ff48 > > If you installed a trial version and your keys have expired, you > can request a trial extension by contacting sales(a)pgroup.com > > 2. If you purchased a license, but have not yet installed your > permanent license keys, please generate and then install your > permanent keys at: > > http://www.pgroup.com/license > > To log in you'll need your PGI PIN and password; these were e- > mailed > to the person who purchased this software. To generate your > permanent keys, you'll also need your host ID. > > Your hostid is 00304857ff48 > > Please contact sales(a)pgroup.com for purchase related inquiries. > > 3. If you have installed your license keys and you are still > receiving > this message, further diagnosis is required. For help on > license > debugging, please check these resources: > > a. Review the PGI installation notes at: > > http://www.pgroup.com/doc/ > > b. Visit the PGI installation FAQ page at: > > http://www.pgroup.com/support/install.htm > > c. Send mail with a description to PGI licensing support at: > > mailto: license(a)pgroup.com > > On Apr 1, 2009, at 11:34 AM, Anthony Chan wrote: > > > > > Hi Dave, > > > > Have you tried the PGI-7.1.6 installed in the MCS machines > > (I checked octagon and octopus) ? > > > > /soft/com/packages/pgi-7.1-6/linux86-64/7.1-6/bin/pgcc > > > > > > A.Chan > > > > ----- "Dave Goodell" <goodell(a)mcs.anl.gov> wrote: > > > >> Does anyone have a modern version of the PGI compilers somewhere? > Or > >> > >> do we know anyone at PGI we could ask for a copy in order to fix > >> compatibility issues like this? > >> > >> -Dave > >> > >> Begin forwarded message: > >> > >>> From: "mpich2" <mpich2-maint(a)mcs.anl.gov> > >>> Date: April 1, 2009 Apr 1 10:07:00 AM CDT > >>> To: undisclosed-recipients: ; > >>> Subject: [mpich2-maint] #509: Cannot build mpich2-1.0.8p1 > (nemesis) > >> > >>> with PGI 8.0-4 on Linux x86_64 > >>> Reply-To: mpich2-maint(a)mcs.anl.gov > >>> > >>> --------------------- > >>> +------------------------------------------------------ > >>> Reporter: goodell | Type: bug > >>> Status: new | Priority: major > >>> Milestone: | Component: mpich2 > >>> --------------------- > >>> +------------------------------------------------------ > >>> > >>> > >>> {{{ > >>> > >>> Begin forwarded message: > >>> > >>>> From: Dave Goodell <goodell(a)mcs.anl.gov> > >>>> Date: April 1, 2009 Apr 1 10:06:09 AM CDT > >>>> To: mpich-discuss(a)mcs.anl.gov > >>>> Subject: Re: [mpich-discuss] Cannot build mpich2-1.0.8p1 > (nemesis) > >>>> with PGI 8.0-4 on Linux x86_64 > >>>> Reply-To: mpich-discuss(a)mcs.anl.gov > >>>> > >>>> On Mar 31, 2009, at 4:21 PM, Gus Correa wrote: > >>>> > >>>>> I decompressed the tarball on a fresh new subdirectory, > >>>>> configured again, ran make again. > >>>>> However, I still get the same exact error. > >>>>> > >>>>> Moreover, the preprocessor macro > >>>>> HAVE_GCC_AND_X86_64_ASM > >>>>> continues not to be defined in the > >>>>> src/include/mpichconf.h file, > >>>>> and most likely continues to be the source for the error. > >>>>> > >>>>> By contrast, configure.in is identical to my patched > >>>>> version (with the pgcc_atomics.patch file). > >>>>> > >>>>> I will send you the output of configure, config.log > >>>>> and src/include/mpichconf.h off list. > >>>>> > >>>>> And here is the "diff" between the configure script from your > >>>>> latest tarball > >>>>> and the configure script from the 1.2.8p1 after I patched it > with > >>>>> pgcc_atomics.patch: > >>>>> > >>>>> [build_pgi-8.0-4]% diff ../configure > /home/swinst/mpich2/1.0.8p1/ > >>>>> mpich2-1.0.8p1/configure29449,29451c29449 > >>>>> > >>>>> Did I do anything wrong? > >>>> > >>>> > >>>> No, I don't think that you did anything wrong. There are just > >> other > >>>> bugs wrt to PGI in our configure logic that I haven't spotted > yet. > >>>> > >>>> This would all go a lot easier if I had a modern PGI compiler > >>>> available for testing. In the mean time, I would recommend just > >>>> editing the generated mpichconf.h after the configure step and > >>>> before the make step to define HAVE_GCC_AND_X86_64_ASM to 1. > That > >>>> ought to fix your immediate problem, although there may be > others > >>>> that will appear once you are over this hurdle. > >>>> > >>>> I'm not sure that there's much more I can do for you in the > short- > >>>> term until I get my hands on a PGI compiler installation. In > the > >>>> medium-term I'll see if I can get this resolved for the 1.1.0 > >> stable > >>>> release (likely some time in May). > >>>> > >>>> Sorry, > >>>> -Dave > >>>> > >>> > >>> }}} > >>> > >>> > >>> -- > >>> Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/509>

2 1

Fwd: [mpich2-maint] #509: Cannot build mpich2-1.0.8p1 (nemesis) with PGI 8.0-4 on Linux x86_64
by Dave Goodell 01 Apr '09

01 Apr '09

Does anyone have a modern version of the PGI compilers somewhere? Or do we know anyone at PGI we could ask for a copy in order to fix compatibility issues like this? -Dave Begin forwarded message: > From: "mpich2" <mpich2-maint(a)mcs.anl.gov> > Date: April 1, 2009 Apr 1 10:07:00 AM CDT > To: undisclosed-recipients: ; > Subject: [mpich2-maint] #509: Cannot build mpich2-1.0.8p1 (nemesis) > with PGI 8.0-4 on Linux x86_64 > Reply-To: mpich2-maint(a)mcs.anl.gov > > --------------------- > +------------------------------------------------------ > Reporter: goodell | Type: bug > Status: new | Priority: major > Milestone: | Component: mpich2 > --------------------- > +------------------------------------------------------ > > > {{{ > > Begin forwarded message: > >> From: Dave Goodell <goodell(a)mcs.anl.gov> >> Date: April 1, 2009 Apr 1 10:06:09 AM CDT >> To: mpich-discuss(a)mcs.anl.gov >> Subject: Re: [mpich-discuss] Cannot build mpich2-1.0.8p1 (nemesis) >> with PGI 8.0-4 on Linux x86_64 >> Reply-To: mpich-discuss(a)mcs.anl.gov >> >> On Mar 31, 2009, at 4:21 PM, Gus Correa wrote: >> >>> I decompressed the tarball on a fresh new subdirectory, >>> configured again, ran make again. >>> However, I still get the same exact error. >>> >>> Moreover, the preprocessor macro >>> HAVE_GCC_AND_X86_64_ASM >>> continues not to be defined in the >>> src/include/mpichconf.h file, >>> and most likely continues to be the source for the error. >>> >>> By contrast, configure.in is identical to my patched >>> version (with the pgcc_atomics.patch file). >>> >>> I will send you the output of configure, config.log >>> and src/include/mpichconf.h off list. >>> >>> And here is the "diff" between the configure script from your >>> latest tarball >>> and the configure script from the 1.2.8p1 after I patched it with >>> pgcc_atomics.patch: >>> >>> [build_pgi-8.0-4]% diff ../configure /home/swinst/mpich2/1.0.8p1/ >>> mpich2-1.0.8p1/configure29449,29451c29449 >>> >>> Did I do anything wrong? >> >> >> No, I don't think that you did anything wrong. There are just other >> bugs wrt to PGI in our configure logic that I haven't spotted yet. >> >> This would all go a lot easier if I had a modern PGI compiler >> available for testing. In the mean time, I would recommend just >> editing the generated mpichconf.h after the configure step and >> before the make step to define HAVE_GCC_AND_X86_64_ASM to 1. That >> ought to fix your immediate problem, although there may be others >> that will appear once you are over this hurdle. >> >> I'm not sure that there's much more I can do for you in the short- >> term until I get my hands on a PGI compiler installation. In the >> medium-term I'll see if I can get this resolved for the 1.1.0 stable >> release (likely some time in May). >> >> Sorry, >> -Dave >> > > }}} > > > -- > Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/509>

3 5