Open MPI logo

Open MPI Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI devel] 1.6.2rc2 VT/OMP build failure with PGI 8.0-6
From: Bert Wesarg (bert.wesarg_at_[hidden])
Date: 2012-09-11 15:29:30


On Tue, Sep 11, 2012 at 9:08 PM, Paul Hargrove <phhargrove_at_[hidden]> wrote:
> While newer PGI compilers don't complain, I find that PGI-8.0-6 fails as
> shown below.
> In addition to 1 error, there are 3 warnings that might be worth
> examination.
>
> My guess is that the code is trying to use OMP features more recent than the
> support provided by this older compiler.
> However, OMPI's README gives the impression that PGI compilers 6.0-5 should
> work.
>
> I also have a PGI-7.2-5 build queued and will follow up with those results
> when available.
>
> -Paul
>
>
>> CXX vtunify-vt_unify_hooks_aevents.o
>>
>> "/users/phargrov/SCRATCH/OMPI/openmpi-1.6.2rc2-linux-x86_64-pgi-8.0/openmpi-1.6.2rc2/ompi/contrib/vt/vt/tools/vtunify/hooks/vt_unify_hooks_aevents.cc",
>> line 69: warning:
>> variable "otf_rc" was set but never used
>> uint8_t otf_rc;
>> ^

They are only checked in assert() statements. I don't know the policy
regarding this for the Open MPI project.

>> "/users/phargrov/SCRATCH/OMPI/openmpi-1.6.2rc2-linux-x86_64-pgi-8.0/openmpi-1.6.2rc2/ompi/contrib/vt/vt/tools/vtunify/hooks/vt_unify_hooks_aevents.cc",
>> line 304: warning:
>> variable "error" was set but never used
>> bool error = false;
>> ^
>>
>> "/users/phargrov/SCRATCH/OMPI/openmpi-1.6.2rc2-linux-x86_64-pgi-8.0/openmpi-1.6.2rc2/ompi/contrib/vt/vt/tools/vtunify/hooks/vt_unify_hooks_aevents.cc",
>> line 336: warning:
>> variable "error" was set but never used
>> bool error = false;
>> ^

Dito for these two warnings.

Bert