On 09/23/2011 09:48 AM, Jeff Squyres wrote:
(...)
> However, we ultimately discarded it when someone showed a real-world code
> that used *multiple* wrapper compilers (i.e., one wrapper compiler invoked
> another, which, in turn, invoked another, and then finally invoked the
> real/underlying
On Sep 23, 2011, at 10:07 AM, Waclaw Kusnierczyk wrote:
> it's not unusual to use double-hyphen ('--') to separate options
> intended for the wrapper from the options intended for the wrapped. so
> you could have
>
>wrapper --foo -- --foo
>
> with the first --foo interpreted by the wrapper
On 09/23/2011 06:40 AM, Jeff Squyres wrote:
(...)
> Unless there is an effort undertaken to standardize wrapper compiler flags,
> this is not going to happen. Indeed, as I mentioned in a prior email, some
> MPI implementations do not have wrapper compilers at all. This makes
> standardizatio
On Sep 23, 2011, at 6:52 AM, Uday Kumar Reddy B wrote:
> But that's not really the point - to re-install MPI from sources! One
> would like to choose between compilers depending on what's on the
> system, and also switch between them to experiment. And if I'm
> packacging a software that makes use
On Sep 23, 2011, at 6:59 AM, Uday Kumar Reddy B wrote:
> MVAPICH, for eg., supports the same set of options as MPICH (-help
> output is identical); so it would be good if you can too. I don't know
> if any other MPIs follow it as well.
That's because MVAPICH is a fork of MPICH.
--
Jeff Squyres
On Fri, Sep 23, 2011 at 3:33 PM, Jeff Squyres wrote:
> On Sep 23, 2011, at 2:04 AM, Uday Kumar Reddy B wrote:
>
>> Okay. BTW, mpicc only has 7 cmdline options, and you probably already
>> support some of them (-show), and they are all provided for good
>> reason.
>
> I assume you mean that *MPICH'
On Fri, Sep 23, 2011 at 2:39 AM, Gus Correa wrote:
> Jeff Squyres wrote:
>>
>> On Sep 22, 2011, at 4:17 PM, Uday Kumar Reddy B wrote:
>>
>>> Yes, but I can't find anything about -cc in openmpi's mpicc man page. So,
>>> -cc should either not be supported or work as per mpich's mpicc if you are
>>>
On Sep 23, 2011, at 2:04 AM, Uday Kumar Reddy B wrote:
> Okay. BTW, mpicc only has 7 cmdline options, and you probably already
> support some of them (-show), and they are all provided for good
> reason.
I assume you mean that *MPICH's* mpicc has 7 command line options. Open MPI's
mpicc only
On Fri, Sep 23, 2011 at 2:55 AM, Jeff Squyres wrote:
> On Sep 22, 2011, at 4:39 PM, Uday Kumar Reddy B wrote:
>
>>> More specifically: how is mpicc supposed to know that any given option was
>>> intended for mpicc and not the underlying compiler, particularly the ones
>>> that it doesn't support
On Sep 22, 2011, at 4:39 PM, Uday Kumar Reddy B wrote:
>> More specifically: how is mpicc supposed to know that any given option was
>> intended for mpicc and not the underlying compiler, particularly the ones
>> that it doesn't support?
>
> Yes, it won't in the general case, but since -cc is a
Jeff Squyres wrote:
On Sep 22, 2011, at 4:17 PM, Uday Kumar Reddy B wrote:
Yes, but I can't find anything about -cc in openmpi's mpicc man page. So, -cc
should either not be supported or work as per mpich's mpicc if you are wrapping
around it.
mpicc has no way of knowing that an option is n
On 09/23/2011 01:49 AM, Jeff Squyres wrote:
On Sep 22, 2011, at 4:17 PM, Uday Kumar Reddy B wrote:
Yes, but I can't find anything about -cc in openmpi's mpicc man page. So, -cc
should either not be supported or work as per mpich's mpicc if you are wrapping
around it.
mpicc has no way of kno
On Sep 22, 2011, at 4:17 PM, Uday Kumar Reddy B wrote:
> Yes, but I can't find anything about -cc in openmpi's mpicc man page. So, -cc
> should either not be supported or work as per mpich's mpicc if you are
> wrapping around it.
mpicc has no way of knowing that an option is not supposed to wor
On Sep 22, 2011, at 2:17 PM, Uday Kumar Reddy B wrote:
>
>
> On 09/23/2011 01:33 AM, Ralph Castain wrote:
>> Ummm...yes, because you are getting the man page for the MPICH mpicc, not
>> ours. Try setting your manpage path to point to the OMPI install directory.
>
> Yes, but I can't find anyth
On 09/23/2011 01:33 AM, Ralph Castain wrote:
Ummm...yes, because you are getting the man page for the MPICH mpicc, not ours.
Try setting your manpage path to point to the OMPI install directory.
Yes, but I can't find anything about -cc in openmpi's mpicc man page.
So, -cc should either not
Ummm...yes, because you are getting the man page for the MPICH mpicc, not ours.
Try setting your manpage path to point to the OMPI install directory.
On Sep 22, 2011, at 1:55 PM, Uday Kumar Reddy B wrote:
> On Fri, Sep 23, 2011 at 1:21 AM, Jeff Squyres wrote:
>> Right: -cc is not an option to
On Fri, Sep 23, 2011 at 1:21 AM, Jeff Squyres wrote:
> Right: -cc is not an option to Open MPI's mpicc wrapper compiler (I don't
> think it ever has been).
But that's not what the manual says ('man mpicc').
--
COMMAND LINE ARGUMENTS
-show - Show the commands that would be us
Right: -cc is not an option to Open MPI's mpicc wrapper compiler (I don't think
it ever has been).
See http://www.open-mpi.org/faq/?category=mpi-apps#cant-use-wrappers and
http://www.open-mpi.org/faq/?category=mpi-apps#override-wrappers-after-v1.0.
On Sep 22, 2011, at 3:44 PM, Uday Kumar Reddy
I have openmpi via the distribution package: openmpi-1.4.3-7.fc14.i686
When attempting to make mpicc use another compiler as follows:
mpicc -cc=icc ...
I get
gcc: unrecognized option '-cc=icc'
/tmp/ccHd339C.o: In function `main':
It looks like it's just passing this as option to gcc instead of
19 matches
Mail list logo
