Hi Aron,
Thanks for the information...everything is clear now.
Hope you will be back to Ireland soon. Sure the weather can be miserable but
nothing beats a good hike in the rain followed by a good pint of Guinness.
Actually Guinness is pretty good with everything including PETSc coding :-)
Reg
Perfect...thanks for the info.
On Wednesday 27 June 2007 14:21, Satish Balay wrote:
> On Wed, 27 Jun 2007, Tim Stitt wrote:
> > Hi PETSc Users/Developers,
> >
> > Could someone explain how I can override the default optimization level
> > that comes with my PETSc build (currently -O). I want to se
Yes. Note that with real number PETSc PetscScalar is exactly an
double and MPIU_SCALAR is exactly MPI_DOUBLE.
Barry
On Wed, 27 Jun 2007, David Fuentes wrote:
>
> Hello,
>
> I need to send a single PetscScalar Value from one processor to another.
>
> I want to use MPI_Send.
>
> Is MPIU_
Yes.
Thanks,
Matt
On 6/27/07, David Fuentes wrote:
>
> Hello,
>
> I need to send a single PetscScalar Value from one processor to another.
>
> I want to use MPI_Send.
>
> Is MPIU_SCALAR the correct MPI_Datatype to MPI_Send a PetscScalar value
> between processors?
>
>
> thank you,
> David
Hello,
I need to send a single PetscScalar Value from one processor to another.
I want to use MPI_Send.
Is MPIU_SCALAR the correct MPI_Datatype to MPI_Send a PetscScalar value
between processors?
thank you,
David Fuentes
Hi PETSc Users/Developers,
Could someone explain how I can override the default optimization level that
comes with my PETSc build (currently -O). I want to set a more aggressive
optimization level (e.g. -O3) for my compiler (PathScale).
Ideally I would prefer a solution which doesn't involve re
And as a correction to my last email, PETSC_ARCH is a 'global'
environment variable, it along with PETSC_DIR help you coordinate
multiple PETSc installations and builds.
~A
On 6/27/07, Aron Ahmadia wrote:
> Dear Tim,
>
> I was just in Ireland a few weeks ago, had a great time climbing
> Carantou
Dear Tim,
I was just in Ireland a few weeks ago, had a great time climbing
Carantouhil and the Pilgrim's Path :D
Have you tried declaring a new $PETSC_ARCH and then overriding the
optimization flags in ./conf/configure? PETSc likes to use the
$PETSC_ARCH flag to maintain all local builds under t
On Wed, 27 Jun 2007, Aron Ahmadia wrote:
> declare -x PETSC_ARCH=petsc_linux_o3
> cd $PETSC_DIR
> ./config/configure.py --COPTFLAGS=-O3
> make
Or you could just do:
./config/configure.py PETSC_ARCH=petsc_linux_o3 COPTFLAGS=-O3
make
Satish
On Wed, 27 Jun 2007, Tim Stitt wrote:
> Hi PETSc Users/Developers,
>
> Could someone explain how I can override the default optimization level that
> comes with my PETSc build (currently -O). I want to set a more aggressive
> optimization level (e.g. -O3) for my compiler (PathScale).
Rebuild a
10 matches
Mail list logo
