changed PETSC_LOGICAL to PETSC_BIT_LOGICAL since it is a bit array and clarifies the difference from PETSC_TRUTH

Hg-commit: 2cdcccc64d1221f8878d4fc690986fe71b961469

PETSC_DLLEXPORT -> PETSCSYS_DLLEXPORT

For consistency with other packages, and since the library is named libpetscsys.

Hg-commit: d411519a6aa3d1f4f3f42dfd9d10e405a0d44202

Commit after merge

Hg-commit: ee2c880beeb7f5709c949b456809141d38ab9b9a

Merge

Hg-commit: f164ce7549fa74f62a595e83f292eeb4d2854681

merge __FUNCT__ checking

Hg-commit: cef89f9215985fa569ef0fe01eb925a548b7801d

better set up for -cuda_synchronize
if log_summary then default to have it on, otherwise default to have it off.
user can set it if they like either way

Hg-commit: 1cbd5c89b8ccbbd8584a6de4cec5

better set up for -cuda_synchronize
if log_summary then default to have it on, otherwise default to have it off.
user can set it if they like either way

Hg-commit: 1cbd5c89b8ccbbd8584a6de4cec5649bcd30e733

show more ...

if -log_summary is used then turn on cuda synchronized because too many people will screw up and get the wrong idea.

Hg-commit: 9d9bc9da4f66e4f3f942eb7c8b29d4d227b980f8

commit after merge

Hg-commit: 4976d5f8a5ede0d2f344004f84eef28988480d5f

Merge

Hg-commit: 9ef83e41d4a8326e1cf5e296edd80e06079632b1

made -cuda_synchronize a command line option

Hg-commit: d5bd0746999ee624a25b123df3ad9464fb299b30

Merge

Hg-commit: 97da7c4ff7039f3498eb4bf946d70f0cc19afa64

cleanup of source for zope

Hg-commit: eb13da4a52adb9db635a651c575f3d0e42ecb70d

Merge

Hg-commit: 3d6e115ed50e0a91aeb25dbd4b36559e2e6d6008

merge

Hg-commit: 05d5009003ecfc80d5043a07199af616ee7c2323

changed PetscGetVersion() to not use unneeded and dangerous PetscStrcat()
added missing \n in PETSc help message
added initial xcode project that builds a simple iphone app

Hg-commit: 66d7e91cc737e8

changed PetscGetVersion() to not use unneeded and dangerous PetscStrcat()
added missing \n in PETSc help message
added initial xcode project that builds a simple iphone app

Hg-commit: 66d7e91cc737e8a060fee138585f89c5bc417239

show more ...

Merge

Hg-commit: 091935e9281c6e900c1e00205f59cde73745cb0d

On May 13, 2010, at 10:48 AM, Jed Brown wrote:

I'm concerned by the following which appears in
PetscAttachDebuggerErrorHandler() and Petsc_MPI_DebuggerOnError():

ierr = PetscAttachDebugger();
if

On May 13, 2010, at 10:48 AM, Jed Brown wrote:

I'm concerned by the following which appears in
PetscAttachDebuggerErrorHandler() and Petsc_MPI_DebuggerOnError():

ierr = PetscAttachDebugger();
if (ierr) { /* hopeless so get out */
MPI_Finalize();
exit(*flag);
}

Since the error handler is not guaranteed to be called collectively, it
seems completely unreasonable to call a collective function, especially
not one with broader scope than PETSC_COMM_WORLD. It seems to me that
the hopeless case should instead call MPI_Abort() on the relevant
communicator.

You are probably right; this code fragment is so old it may have been written before I knew what MPI_Abort() was. I am changing it.


Similarly, why does Petsc_MPI_AbortOnError() call abort()
instead of MPI_Abort()?

I think this is clearly documented in the comment above it. Here is the comment:

This is so MPI errors in the debugger will leave all the stack
frames. The default abort cleans up and exits.

You use this error handler if you are running in the debugger (for example with -start_in_debugger). If you call MPI_Abort() it cleans up and you get no useful stack information in the debugger. I will change the comment to:

This is so MPI errors in the debugger will leave all the stack
frames. The default MP_Abort() cleans up and exits thus providing no useful information
in the debugger hence we call abort() instead of MPI_Abort().

Is it clear now, or am I missing something?

Barry

Hg-commit: 4663027817c3c85b7bd6d5229eb182ec49e8cf67

show more ...

commit after merge

Hg-commit: 2ef3359e5b95ab3dd364cca5103b3c9cd01e67aa

Merge

Hg-commit: 55b7a9d1500c75e20db02f207b9744d4e56162d1

Make error macros nest in cascading if statements, revert Hong's reversion of Barry's breakage

The

#define MACRO(x,y) do { multiple(x); statements(y); } while (0)

construct requires the user to

Make error macros nest in cascading if statements, revert Hong's reversion of Barry's breakage

The

#define MACRO(x,y) do { multiple(x); statements(y); } while (0)

construct requires the user to provide a closing semicolon (this patch
fixes this problem in many places), and does the correct thing in
cascading if statements. Note that the alternative

#define MACRO(x,y) { multiple(x); statements(y); }

expands

if (cond) MACRO(x);
else other();

as

if (cond) { multiple(x); statements; }
;
else other();

and the final statement is an else with no matching if. I suggest that
PETSc adopt the do {} while (0) construct anywhere that it currently
uses compound statements within unguarded braces (note that most PETSc
macros return a value and thus do not have this problem).

Hg-commit: ecf653b2f268465b7e7cb7569f7b80897acb163a

show more ...

added MPI_Comm as first argument to PetscError() and SETERRQX()

Hg-commit: fe5a2ff050abc00ca2c2979c0af22b117b62874e

Move processing of -fp_trap to come after pushing other signal handlers

This prevents the trapping signal handler for SIGFPE from being overwritten
by the default handler which can't provide a usefu

Move processing of -fp_trap to come after pushing other signal handlers

This prevents the trapping signal handler for SIGFPE from being overwritten
by the default handler which can't provide a useful error message.

Note that the lack of interoperability between PetscPushSignalHandler
and floating point handlers is a deficiency in the interface for the
former. All the solutions I can think of would add nontrivial
complexity so I'm not implementing them now.

Hg-commit: 97a23cb8dc137879bc69e35ee6a7c964fcfff5ee

show more ...

detect valgrind/valgrind.h if it exists and turn off default -malloc when valgrind is running

Hg-commit: 021c9b45f2e46b0e6cab7bdf08a39cd86f607413

Merge.

Hg-commit: 96dff560e9caff2ee6539fb4c50e92b67324e0b0

updated all references to troubleshooting.html to faq.html since troubleshooting.html is removed

Hg-commit: f2ea5979ffd78c204cf4d8039a401151639db052