July 2022 Archives by subject

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...

Starting: Fri Jul 1 22:49:19 CDT 2022
Ending: Sun Jul 31 16:31:51 CDT 2022
Messages: 105

• [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS)   LEDAC Pierre
• [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS)   Barry Smith
• [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS)   Matthew Knepley
• [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS)   Satish Balay
• [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS)   LEDAC Pierre
• [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS)   Satish Balay
• [petsc-dev] [Minor issue] Lag during PetscInitialize on Fedora 36 (never seen before with other OS)   Satish Balay
• [petsc-dev] FindPETSc.cmake   Barry Smith
• [petsc-dev] GPU performance of MatSOR()   Han Tran
• [petsc-dev] GPU performance of MatSOR()   Jed Brown
• [petsc-dev] GPU performance of MatSOR()   Barry Smith
• [petsc-dev] GPU performance of MatSOR()   Paul Mullowney
• [petsc-dev] GPU performance of MatSOR()   Jed Brown
• [petsc-dev] Hiptmair--Xu as PCCOMPOSITE   Pierre Jolivet
• [petsc-dev] Hiptmair--Xu as PCCOMPOSITE   Mark Adams
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Fande Kong
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Barry Smith
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Fande Kong
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Satish Balay
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Satish Balay
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Satish Balay
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Fande Kong
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Satish Balay
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Barry Smith
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Satish Balay
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Satish Balay
• [petsc-dev] ld: warning: could not create compact unwind for _dgeev_: registers 27 and 28 not saved contiguously in frame   Satish Balay
• [petsc-dev] macOS $ ./ex69 dyld[93174]: symbol not found in flat namespace '___mumps_ana_ord_wrappers_MOD_mumps_metis_nodend_mixedto32' Abort trap: 6   Barry Smith
• [petsc-dev] macOS $ ./ex69 dyld[93174]: symbol not found in flat namespace '___mumps_ana_ord_wrappers_MOD_mumps_metis_nodend_mixedto32' Abort trap: 6   Stefano Zampini
• [petsc-dev] macOS $ ./ex69 dyld[93174]: symbol not found in flat namespace '___mumps_ana_ord_wrappers_MOD_mumps_metis_nodend_mixedto32' Abort trap: 6   Barry Smith
• [petsc-dev] MatProduct_AtB --with-scalar-type=complex   Pierre Jolivet
• [petsc-dev] MatProduct_AtB --with-scalar-type=complex   Barry Smith
• [petsc-dev] MatProduct_AtB --with-scalar-type=complex   Zhang, Hong
• [petsc-dev] MatProduct_AtB --with-scalar-type=complex   Pierre Jolivet
• [petsc-dev] MatProduct_AtB --with-scalar-type=complex   Zhang, Hong
• [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner   Pierre Jolivet
• [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner   Barry Smith
• [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner   Matthew Knepley
• [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner   Pierre Jolivet
• [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner   Barry Smith
• [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner   Barry Smith
• [petsc-dev] PCFIELDSPLIT with inner -ksp_reuse_preconditioner   Matthew Knepley
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Kaus, Boris
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Matthew Knepley
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jacob Faibussowitsch
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jacob Faibussowitsch
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Matthew Knepley
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jacob Faibussowitsch
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jacob Faibussowitsch
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jeremy L Thompson
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jed Brown
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Boyce Griffith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Scott Kruger
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Boyce Griffith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Eric Chamberland
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jed Brown
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Justin Chang
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jed Brown
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jed Brown
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Ham, David A
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Matthew Knepley
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Lisandro Dalcin
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jacob Faibussowitsch
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Lisandro Dalcin
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Matthew Knepley
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Lisandro Dalcin
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jed Brown
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jacob Faibussowitsch
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jacob Faibussowitsch
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Jacob Faibussowitsch
• [petsc-dev] PETSc future starting as a new design layer that runs on top of PETSc 3?   Barry Smith
• [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus   Jed Brown
• [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus   Matthew Knepley
• [petsc-dev] Problem with unnamed side sets in DMPlexCreateExodus   David Andrs
• [petsc-dev] proposed minor PetscPartitioner changes   Eric Chamberland
• [petsc-dev] Reformatting all PETSc source code with clang-format   Barry Smith
• [petsc-dev] searching for petsc4py on petsc.org/main finds nothing   Barry Smith
• [petsc-dev] test failure in main   Blaise Bourdin
• [petsc-dev] test failure in main   Barry Smith
• [petsc-dev] test failure in main   Satish Balay
• [petsc-dev] VecNest   Pierre Jolivet
• [petsc-dev] VecNest   Mark Adams
• [petsc-dev] VecNest   Pierre Jolivet
• [petsc-dev] VecNest   Pierre Jolivet
• [petsc-dev] VecNest   Matthew Knepley
• [petsc-dev] VecNest   Pierre Jolivet
• [petsc-dev] VecNest   Matthew Knepley
• [petsc-dev] VecNest   Matthew Knepley
• [petsc-dev] VecNest   Pierre Jolivet
• [petsc-dev] VecNest   Matthew Knepley

Last message date: Sun Jul 31 16:31:51 CDT 2022
Archived on: Sun Jul 31 23:14:44 CDT 2022

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...