[petsc-dev] [GPU] Performance on Fermi
Barry Smith
bsmith at mcs.anl.gov
Fri Aug 27 19:00:03 CDT 2010
On Aug 27, 2010, at 4:34 PM, Keita Teranishi wrote:
> Jed,
>
> I usually manually edit petscconf.h and petscvariables to change the installation configurations for Cray XT/XE. The problem is configure script of PETSc picks up wrong variables and #define macros because the OS and library setting on the login node is different from the compute node.
Keita,
We would prefer that you complain to petsc-maint at mcs.anl.gov so that we can fix configure problems and not have anyone editing the generated files.
Barry
1) so that it works for all users not just those that know how to edit those files. We cannot fix problems we don't know about
2) editing those files repeatedly is fragile and it is easy to make a slight mistake that's hard to track down.
>
> This particular case is just a mistake in configure script (and it's not a big deal to fix), but it will be great if you have any ideas to avoid picking up wrong settings.
>
> Thanks,
> ================================
> Keita Teranishi
> Scientific Library Group
> Cray, Inc.
> keita at cray.com
> ================================
>
>
> -----Original Message-----
> From: Jed Brown [mailto:five9a2 at gmail.com] On Behalf Of Jed Brown
> Sent: Friday, August 27, 2010 4:29 PM
> To: Keita Teranishi; For users of the development version of PETSc
> Subject: RE: [petsc-dev] [GPU] Performance on Fermi
>
> On Fri, 27 Aug 2010 16:18:43 -0500, Keita Teranishi <keita at cray.com> wrote:
>> Yes, I replaced all the compiler flags by -O3.
>
> petsc-maint doesn't come to me, but if the snippet that Barry quoted was
> from your log_summary, then PETSC_USE_DEBUG was definitely defined when
> plog.c was compiled. It's really much easier to have two separate
> builds and always use the optimized one when profiling.
>
> Jed
More information about the petsc-dev
mailing list