Hi,

Am 01.02.2014 um 15:10 schrieb Jiri Kraus:

> sorry but I don't know the details of the issue. But although the error is 
> reported as pgc++ not being link compatible to pgcc by OpenMPI configure the 
> error in the config.log is a complier error. So I don't think that this is a 
> linking issue. 
> 
> > When I get it right, it should be a feature of `pgc++` to be link 
> > compatible with `gcc`, while `pgcpp` links with `pgcc` objects.
> 
> To my understanding C compliers like gcc and pgcc do not have the linking 
> issues that C++ compliers have they simply follow the ABI of the OS and do 
> not have name mangling issues. So most C compliers are link compatible. And 
> you can link C code from C++. The C++ compiler just needs to know that 
> something C and not C++ is used (extern "C" is used for this).
> Because of function overloading, Templates and maybe other things, I am not 
> aware of, C++ needs name mangling to encode these information. And here pgcpp 
> and pgc++ implement different ABI's and name mangling schemes. pgc++ 
> implements the same ABI as g++ and thus is link compatible with g++. On the 
> other hand pgcpp implements its own ABI and is compatible with itself. 

thx for this clarification.

-- Reuti


> Jiri
> 
> Sent from my Nexus 7, I apologize for spelling errors and auto correction 
> typos.
> 
> -----Original Message-----
> Date: Fri, 31 Jan 2014 22:50:40 +0100
> From: Reuti <re...@staff.uni-marburg.de>
> To: Open MPI Users <us...@open-mpi.org>
> Subject: Re: [OMPI users] Compiling OpenMPI with PGI pgc++
> Message-ID: <abe8d68f-f09c-4846-b696-9b514dac8...@staff.uni-marburg.de>
> 
> Content-Type: text/plain; charset=us-ascii
> 
> 
> 
> Hi,
> 
> 
> 
> Am 31.01.2014 um 18:59 schrieb Jiri Kraus:
> 
> 
> 
> > Thanks for taking a look. I just learned from PGI that this is a known bug 
> > that will be fixed in the 14.2 release (Februrary 2014).
> 
> 
> 
> Will `pgc++` then link to `gcc` or `pgcc`? When I get it right, it should be 
> a feature of `pgc++` to be link compatible with `gcc`, while `pgcpp` links 
> with `pgcc` objects.
> 
> 
> 
> -- Reuti
> 
> 
> 
> 
> 
> > Thanks 
> 
> > 
> 
> > Jiri
> 
> > 
> 
> >> -----Original Message-----
> 
> >> Date: Wed, 29 Jan 2014 18:12:46 +0000
> 
> >> From: "Jeff Squyres (jsquyres)" <jsquy...@cisco.com>
> 
> >> To: Open MPI Users <us...@open-mpi.org>
> 
> >> Subject: Re: [OMPI users] Compiling OpenMPI with PGI pgc++
> 
> >> Message-ID: <556094df-cd27-4908-aec1-a6ad9efb6...@cisco.com>
> 
> >> Content-Type: text/plain; charset="us-ascii"
> 
> >> 
> 
> >> On Jan 29, 2014, at 12:35 PM, Reuti <re...@staff.uni-marburg.de> wrote:
> 
> >> 
> 
> >>>> I don't know the difference between pgc++ and pgcpp, unfortunately.
> 
> >>> 
> 
> >>> It's a matter of the ABI:
> 
> >>> 
> 
> >>> http://www.pgroup.com/lit/articles/insider/v4n1a2.htm
> 
> >>> 
> 
> >>> pgc++ uses the new ABI.
> 
> >> 
> 
> >> 
> 
> >> Must be more than that -- this is a compile issue, not a link issue.
> 
> >> 
> 
> >> --
> 
> >> Jeff Squyres
> 
> >> jsquy...@cisco.com
> 
> >> For corporate legal information go to:
> 
> >> http://www.cisco.com/web/about/doing_business/legal/cri/
> 
> > NVIDIA GmbH, Wuerselen, Germany, Amtsgericht Aachen, HRB 8361
> 
> > Managing Director: Karen Theresa Burns
> 
> > 
> 
> > -----------------------------------------------------------------------------------
> 
> > This email message is for the sole use of the intended recipient(s) and may 
> > contain
> 
> > confidential information. Any unauthorized review, use, disclosure or 
> > distribution
> 
> > is prohibited. If you are not the intended recipient, please contact the 
> > sender by
> 
> > reply email and destroy all copies of the original message.
> 
> > --------------------------------------------------------------------------------
> 
> 
> Sent from my Nexus 7, I apologize for spelling errors and auto correction 
> typos.
> _______________________________________________
> users mailing list
> us...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/users

Reply via email to