Re: [OMPI devel] opal / fortran / Flogical

2009-06-02 Thread Jeff Squyres
It looks like Rainer reverted the stuff in r21342. Rainer -- is it safe for Ralph to move the arch.c stuff back up into OMPI, or will that conflict with your stuff? On Jun 1, 2009, at 11:12 PM, Ralph Castain wrote: Just to throw some $0.002 into this overall discussion... Not knowing this

Re: [OMPI devel] opal / fortran / Flogical

2009-06-02 Thread Rainer Keller
On Tuesday 02 June 2009 07:48:02 am Jeff Squyres wrote: > It looks like Rainer reverted the stuff in r21342. Yes. > Rainer -- is it safe for Ralph to move the arch.c stuff back up into > OMPI, or will that conflict with your stuff? Yes, we use it. Please leave it at the OPAL layer. We need a way t

Re: [OMPI devel] opal / fortran / Flogical

2009-06-02 Thread Jeff Squyres
On Jun 2, 2009, at 9:08 AM, Rainer Keller wrote: > Rainer -- is it safe for Ralph to move the arch.c stuff back up into > OMPI, or will that conflict with your stuff? Yes, we use it. Please leave it at the OPAL layer. We need a way to describe and store the remote architecture at the OPAL lay

Re: [OMPI devel] opal / fortran / Flogical

2009-06-02 Thread Rainer Keller
Hi Jeff, no, that's not an issue. The comment is correct: For any Fortran integer*kind we need to have _some_ C-representation as well, otherwise we disregard the type (tm), see e.g. the old and resolved ticket #1094. The representation chosen is set in opal/util/arch.c and is conclusive as far

Re: [OMPI devel] opal / fortran / Flogical

2009-06-02 Thread George Bosilca
The datatype engine (where the arch code was originally from), needs a way to describe the architectures in order to know how to convert the data. Therefore I will advocate the return of the opal/util/arch.h back in the datatype. george. On Jun 2, 2009, at 07:24 , Rainer Keller wrote:

Re: [OMPI devel] opal / fortran / Flogical

2009-06-02 Thread Ralph Castain
Please feel free to do so, George, as far as I'm concerned. I will modify the ORTE code in anticipation of it by removing the arch-related calls. Should have that for you later today or tomorrow. If it doesn't move, no harm done - like I said, I really don't need it any more, but was suggesting th

Re: [OMPI devel] opal / fortran / Flogical

2009-06-02 Thread Ralph Castain
Quick question, George - are you planning on leaving that arch computation in OPAL, but just moving it to the new opal/datatype area? If so, then I won't worry about removing the arch-related calls from ORTE right away. If you are planning on moving it back to OMPI, then I'll put my efforts at a h

Re: [OMPI devel] opal / fortran / Flogical

2009-06-02 Thread George Bosilca
Ralph, The plan was to leave the arch detection down in OPAL, but instead of util to move it back in the datatype. Therefore, all references to the arch in ORTE are safe. Thanks, george. On Jun 2, 2009, at 15:31 , Ralph Castain wrote: Quick question, George - are you planning on lea