[petsc-dev] Building PETSc with PGI Compilers

[Cortese . Thomas]

Do you mean

CC = /path/to/pgcc



p.s.  I am almost certainly leaving my current position at the end of the year; could my petsc-dev email address be changed to

tcortese at illinoisalumni.org

Thanks,

    -Tom Cortese
________________________________
From: petsc-dev-bounces at mcs.anl.gov [petsc-dev-bounces at mcs.anl.gov] on behalf of Jed Brown [jedbrown at mcs.anl.gov]
Sent: Thursday, December 22, 2011 10:43 PM
To: For users of the development version of PETSc
Subject: Re: [petsc-dev] Building PETSc with PGI Compilers

On Thu, Dec 22, 2011 at 22:18, Dave Nystrom <dnystrom1 at comcast.net<mailto:dnystrom1 at comcast.net>> wrote:
--with-gnu-compilers=0 --with-vendor-compilers=pgi

--with-vendor-compilers=portland

just instructs BuildSystem to look for pgcc. You might be better off specifying the path of the specific compiler you want to use:

CFLAGS=/path/to/pgcc


I want to try building PETSc with the PGI compilers so I can use vendor blas
with the external direct solver packages.

This should definitely not be necessary. You should be able to link vendor BLAS with any compiler.

 I'm also interested in seeing what
difference PETSc in general would see in performance for PGI versus GNU.

I have always found PGI to be a waste of time.
________________________________
This electronic message transmission and any attachments that accompany it contain information from DRC® (Dynamics Research Corporation) or its subsidiaries, or the intended recipient, which is privileged, proprietary, business confidential, or otherwise protected from disclosure and is the exclusive property of DRC and/or the intended recipient. The information in this email is solely intended for the use of the individual or entity that is the intended recipient. If you are not the intended recipient, any use, dissemination, distribution, retention, or copying of this communication, attachments, or substance is prohibited. If you have received this electronic transmission in error, please immediately reply to the author via email that you received the message by mistake and also promptly and permanently delete this message and all copies of this email and any attachments. We thank you for your assistance and apologize for any inconvenience.