search for: pgi

Hi everyone, I have some very good news for everyone interested a production-quality Fortran frontend for LLVM: The U.S. Department of Energy’s National Nuclear Security Administration and its three national labs have reached an agreement with NVIDIA's PGI division to adapt and open-source PGI's Fortran frontend, and associated Fortran runtime library, for contribution to the LLVM project. PGI is now working on isolating the necessary frontend components from their existing compiler code base and adapting those components to produce LLVM IR for c...

...y" <asb at asbradbury.org> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "LLVM Dev" <llvm-dev at lists.llvm.org>, "flang-dev" <flang-dev at googlegroups.com>, "Rob Neely" <neely4 at llnl.gov>, > "douglas miles (PGI)" <douglas.miles at pgroup.com> > Sent: Saturday, November 14, 2015 1:41:08 AM > Subject: Re: [llvm-dev] Adapting and open-sourcing PGI's Fortran frontend for LLVM > > On 13 November 2015 at 22:22, Hal Finkel via llvm-dev > <llvm-dev at lists.llvm.org> wrote: &g...

Hello! I am updating to the R-devel version as of 2/28 and recompiling with OpenBLAS. I got that to compile nicely. I am now updating a package that uses the OpenBLAS and the PGI compiler, which has changed too. I just changed the path names in Makevars. Here is the Makevars file. FC= d:/PGI/win64/18.10/bin/pgf90 F77= d:/PGI/win64/18.10/bin/pgf90 CC = d:/PGI/win64/18.10/bin/pgcc FFLAGS= -Ld:/PGI/win64/18.10/bin/pgf90.dll -Ld:/PGI/win64/18.10/bin/pgc14.dll FLIBS= -Ld:/PGI...

Hi Chad - We have a functional Fortran compiler, with the PGI front-end bridged directly to LLVM, all of our Fortran runtime libraries integrated, and the Clang driver adapted for use with the Fortran compiler. We're working with a few users at DOE who are trying to compile big applications with a binary version of the compiler. Work is ongoing to migra...

Hi Chad, I can tell you that progress is being made on PGI's side; I'll let Doug/Rob provide more detailed updates. -Hal ----- Original Message ----- > From: "Chad Rosier" <mcrosier at codeaurora.org> > To: "Hal Finkel" <hfinkel at anl.gov> > Cc: "flang-dev" <flang-dev at googlegroups.com>...

Chad, et al, In addition to Doug’s excellent technical update, I’ll note that we are starting to have some discussions on the DOE side with PGI about establishing a more formal review team made up of some key LLVM stakeholders to help smooth the way for a broader public rollout of the Flang code base and eventual integration. We’ll probably rely on Hal and others here to help us figure out who that group might be. My expectation is that it...

...---- From: llvm-dev [mailto:llvm-dev-bounces at lists.llvm.org] On Behalf Of Chris Lattner via llvm-dev Sent: Sunday, November 15, 2015 12:46 AM To: Hal Finkel <hfinkel at anl.gov> Cc: LLVM Dev <llvm-dev at lists.llvm.org>; flang-dev <flang-dev at googlegroups.com>; douglas miles (PGI) <douglas.miles at pgroup.com>; Rob Neely <neely4 at llnl.gov> Subject: Re: [llvm-dev] Adapting and open-sourcing PGI's Fortran frontend for LLVM > On Nov 13, 2015, at 2:22 PM, Hal Finkel via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi everyone, > >...

> On May 26, 2016, at 1:57 PM, Neely, Rob via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Chad, et al, > > In addition to Doug’s excellent technical update, I’ll note that we are > starting to have some discussions on the DOE side with PGI about > establishing a more formal review team made up of some key LLVM > stakeholders to help smooth the way for a broader public rollout of the > Flang code base and eventual integration. We’ll probably rely on Hal and > others here to help us figure out who that group might be. My ex...

Hi All, While attempting to build R-patched using the Portland Group compiler suite on our dual Opteron 250 box running Scyld 29cz5 (based on RH, kernel 2.4.29), I get: make[5]: Leaving directory `/home/andy/Rbuild/R221-pgi/src/library/tools/src' make[5]: Entering directory `/home/andy/Rbuild/R221-pgi/src/library/tools/src' pgcc -I../../../../include -I/include -I/include/CC -fpic -O2 -Kieee -c /home/andy/Rbuild/R-patched/src/library/tools/src/text.c -o text.o pgcc -I../../../../include -I/include -I/incl...

...>> On May 26, 2016, at 1:57 PM, Neely, Rob via llvm-dev >><llvm-dev at lists.llvm.org> wrote: >> >> Chad, et al, >> >> In addition to Doug’s excellent technical update, I’ll note that we are >> starting to have some discussions on the DOE side with PGI about >> establishing a more formal review team made up of some key LLVM >> stakeholders to help smooth the way for a broader public rollout of the >> Flang code base and eventual integration. We’ll probably rely on Hal and >> others here to help us figure out who that group...

All excellent news! Thanks for the update, Doug! -----Original Message----- From: douglas miles (PGI) [mailto:douglas.miles at pgroup.com] Sent: Thursday, May 26, 2016 2:58 PM To: Hal Finkel <hfinkel at anl.gov>; mcrosier at codeaurora.org Cc: flang-dev <flang-dev at googlegroups.com>; Rob Neely <neely4 at llnl.gov>; Chris Lattner <clattner at apple.com>; llvm-dev at lists...

Dear R-devel, [I'm not sure if this is appropriate for R-devel. If not, I'm more than happy to move it to R-help.] As those of you who saw my post on R-help know, I've been trying to build R-patched on a dual Opteron box running Scyld Beowulf, using the PGI 6.1 compilers. The build went fine, but I couldn't get it to pass make check-all. Jennifer Lai, who reported success with PGI 6.0 previously, seems to have the same problem with 6.1. Here are the particulars: Since R requires IEEE754 conformance, the flag to use for PGI is -Kieee. (BTW, con...

...016, at 1:57 PM, Neely, Rob via llvm-dev >>><llvm-dev at lists.llvm.org> wrote: >>> >>> Chad, et al, >>> >>> In addition to Doug’s excellent technical update, I’ll note that we are >>> starting to have some discussions on the DOE side with PGI about >>> establishing a more formal review team made up of some key LLVM >>> stakeholders to help smooth the way for a broader public rollout of the >>> Flang code base and eventual integration. We’ll probably rely on Hal and >>> others here to help us figure ou...

Hello I would like to build R from source and use the PGI compiler, rather than the GCC compiler. I saw the instructions for the Intel compiler in the R Installation Manual, but I didn't see the PGI. I tried a few times without instructions, but without success. Any suggestions would be most welcome. Also, I hope this is the right group for the qu...

...t; wrote: > > Hi everyone, > > I have some very good news for everyone interested a production-quality Fortran frontend for LLVM: > > The U.S. Department of Energy’s National Nuclear Security Administration and its three national labs have reached an agreement with NVIDIA's PGI division to adapt and open-source PGI's Fortran frontend, and associated Fortran runtime library, for contribution to the LLVM project. PGI is now working on isolating the necessary frontend components from their existing compiler code base and adapting those components to produce LLVM IR for c...

Hi, Can anyone advise me on how to compile R with Portland Group compiler on a Opeteron machine with Red Hat Enterprise Linux WS release 4 installed? I've edit config.site file to pick portland group compilers instead of gcc. Here is the list of modified flags: CC=/usr/pgi/linux86-64/6.0/bin/pgcc CFLAGS='-g -O2' CPPFLAGS='-I/usr/pgi/linux86-64/6.0/include -I/usr/pgi/linux86-64/6.0/include/CC' F77=/usr/pgi/linux86-64/6.0/bin/pgf77 FLAGS='-O2' CPICFLAGS=-fPIC FPICFLAGS=-fPIC SHLIB_LDFLAGS=-shared LDFLAGS='-L/usr/pgi/linux86-64/6.0/lib -L/us...

...nd the notes from Jennifer Lai on p33 of "R Installation and Administration" version 2.3.0 (2006-04-24). I have not used this compiler before, so it is possible things are messed up more than usual, even for me. Following the R Installation and Administration notes I set export PGI=/usr/pgi/linux86-64/6.1 export PATH=$PGI/bin:$PATH export MANPATH=$MANPATH=$PGI/man:/ export CC=pgcc export CFLAGS="-g -O2 -Kieee" export CPPFLAGS="-I$PGI/include -I$PGI/include/CC" export F77=pgf77 export FFLAGS="-g -O2 -Kieee&quot...

Hi, Has anyone had any luck in using portland group compiler to build R(-devel) with AMD's pgi compiled ACML library? I've downloaded the packages and set LD_LIBRARY_PATH, and run configuration script as follow: % ./configure --prefix=/usr/local/R.pgcc --with-blas='-lacml' However, it failed to pick up double complex BLAS, checking for sgemm_ in -lacml... yes checking whether...

Dear R-help, I am trying to build R-2.2.0-patched (2005-11-07 r36217) on the head node of a Scyld cluster (dual Opteron 250s) using PGI compilers (v6.0). I used the flags suggested by Jennifer Lai on R-devel (taken from R-admin, except that I had to add -L/usr/X11R6/lib64 to LDFLAGS). The build went fine, but make check-all failed when running tests/Examples/graphics-Ex.R, at: > plot(1:2, xaxs = "i") # 'inner-ax...

...m trying to compile R-devel (R-devel_2006-05-17.tar.gz) on Red Hat Enterprise Linux AS release 3 (Taroon Update 7) using the Portland Group compiler 6.0. (I have not yet successful compiled R on this configuration, so I don't know if this is a new problem.) I get an error pgcc -L/usr/local/pgi/linux86-64/6.0/libso -L/usr/lib64 -o dftables dftables.o ../dftables chartables.h ../dftables: error while loading shared libraries: libpgc.so: cannot open shared object file: No such file or directory make[3]: *** [chartables.h] Error 127 The library containing libpgc.so is in both my LD_LIBRA...