Re: [OMPI devel] RFC: dead code removal

2013-05-15 Thread Jeff Squyres (jsquyres)
Sure, no problem. On May 15, 2013, at 8:41 PM, Ralph Castain wrote: > Hmmm...some of this doesn't look right to me. It could be that some of the > code changed and stale things didn't get removed, but the snippets of logic > in your patch raise alarms in some cases. > > Can you allow a bit m

Re: [OMPI devel] RFC: dead code removal

2013-05-15 Thread Ralph Castain
Hmmm...some of this doesn't look right to me. It could be that some of the code changed and stale things didn't get removed, but the snippets of logic in your patch raise alarms in some cases. Can you allow a bit more time? I need to apply the patch and actually look at the total code path to u

[OMPI devel] RFC: dead code removal

2013-05-15 Thread Jeff Squyres (jsquyres)
WHAT: Remove a bunch of "set but not used" variables / dead code WHY: Because it's dead code WHERE: All over, but NOT the BTL ALLOC macros (per prior argu^H^H^H^Hdiscussion) WHEN: Tomorrow (16 May 2013), COB More detail: gcc 4.7.x squawks a lot about "set but unused" variables. I took a sweep

[OMPI devel] 1.7.2rc1

2013-05-15 Thread Ralph Castain
Hi folks We have posted the first release candidate for the 1.7.2 release in the usual place: http://www.open-mpi.org/software/ompi/v1.7/ Please put it thru the wringer to help us validate it prior to release. Thanks Ralph

[OMPI devel] RFC: Remove old MCA parameter system from trunk

2013-05-15 Thread Nathan Hjelm
What: The mca_base_var_* API replaces the mca_base_var_* API. A support layer for the old API currently resides in the trunk. I will remove the layer from the trunk and replace any remaining mca_base_param_* calls with their equivalents in the new API. The support layer will remain for the 1.7/1