s to keep track of, and add special rules
for all these compilers (and versions). Since there is no clear answer we have
found it’s easier to punt responsibility to the user.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Aug 8, 2023, at 12:35, Liu Wei AWE v
th
clang-format-diff
(https://clang.llvm.org/docs/ClangFormat.html#script-for-patch-reformatting).
I floated the idea of adding git hooks ages ago, but it was shot down for some
reason.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jun 18, 2023, at 16:33, Barry
ich takes ages and seems to also build the old style html documentation. Is
> this right?
I think you can just do
$ cd ${PETSC_DIR}
$ make docs
This has the added benefit of doing it all in a venv so you don’t pollute your
regular python install.
Best regards,
Jacob Faibussowitsch
(Jac
What is your full linker command? Make sure it also contains -fsanitize=address
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jun 13, 2023, at 11:05, Matthew Knepley wrote:
>
> For some reason, libCEED seems broken with Address
ll you this.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Feb 23, 2023, at 12:59, Barry Smith wrote:
>
>
> Jacob,
>
> When I am adding code it makes sense that the new code I just added is
> tested, at least to some degree, on my ma
> But I'd like a short term solution for the current design bug, so I'll
> eventually try a minimal change to the code.
There is nothing is more permanent than a temporary solution.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jan 22, 2023, at 20:12, Ba
rds,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Nov 4, 2022, at 09:02, Stefano Zampini wrote:
>
> Look at the stacktrace. It is all petsc. Who is supposed to be this someone?
>
> On Fri, Nov 4, 2022, 15:07 Jacob Faibussowitsch wrote:
> I’ve seen these too.
c-ma...@mcs.anl.gov--\n");
PetscErrorPrintfNormal();
}
}
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Nov 4, 2022, at 05:06, Stefano Zampini wrote:
>
> What does the message imply? That PETSc error handler is misbehaving? or that
> the user code is wrong
This smells like a bug in clang-format. Could also be worth opening an issue at
https://github.com/llvm/llvm-project
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Aug 21, 2022, at 19:27, Barry Smith wrote:
>
>
>
>
> if (xxx)
r this look like? The
AST will give you none of this information.
You can kind of get around this using type annotations but those are in no way
binding, so need to be checked at runtime (by us) anyways.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jul 31, 2022, at
ibrary extremely limiting. Not to mention the
cause of a huge number of newby bugs, because you have to reinvent the wheel on
data structures that have been around since the stone ages.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jul 31, 2022, at 12:31, Jacob Faibu
optimizes almost nothing because you can never be sure that an expression
doesn’t have a side-effect.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jul 31, 2022, at 12:09, Barry Smith wrote:
>
>
>> My issue with C++ is not the language itsel
e I didn’t read this :)
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jul 31, 2022, at 09:17, Lisandro Dalcin wrote:
>
>
>
> On Tue, 26 Jul 2022 at 17:35, Barry Smith wrote:
>
> Bindings for Fortran 20xx, Python 3, Julia? If the bindings
d
by construction via smart pointers. Making it impossible not to clean up after
yourself via RAII.
All “modern” C++ does is make the above more ergonomic and easier to do.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jul 26, 2022, at 09:55, Barry Smith wrote:
rom C++ then you can simply overload (no need for
macros).
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jul 26, 2022, at 09:51, Matthew Knepley wrote:
>
> On Tue, Jul 26, 2022 at 8:44 AM Jacob Faibussowitsch
> wrote:
> > even more importantly
nds would need to stay (unless we mandate C++23
https://en.cppreference.com/w/cpp/utility/basic_stacktrace) but now that they
are uniform it would also not be difficult to factor them out again.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jul 26, 2022, at
among all choices given, and
given the heavy buy-in from corporate America we are guaranteed that C++ will
see continued support for years (if not decades) to come.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jul 26, 2022, at 08:30, Matthew Knepley wr
rop-down that has “Assigned to you” and “Review requests for you”.
Clicking the latter gives you a list of all MR’s where you are set as a
reviewer.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On May 25, 2022, at 11:57, Matthew Knepley wrote:
>
> On Wed,
`
So the idea instead was to have a `PetscSafeCall()` but with less typing. It
also fit with the previous `PetscStackCall()` family. You can find the naming
discussion here
https://gitlab.com/petsc/petsc/-/merge_requests/4889#note_854556084
Best regards,
Jacob Faibussowitsch
(Jacob Fai - boos
warnings) since they are so widely used.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Apr 26, 2022, at 17:36, Hammond, Glenn E via petsc-dev
> wrote:
>
> PETSc,
>
> I see that CHKERRQ is back in the Fortran interface after 3.17.1. Will
> CHKERRQ be
on this
though).
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Apr 26, 2022, at 09:48, Jose E. Roman wrote:
>
> You have to add -log_view_gpu_time
> See https://gitlab.com/petsc/petsc/-/merge_requests/5056
>
> Jose
>
>
>> El 26 abr 2022, a l
lustrated some evolution of
abstraction for a single particular problem. Start from finite difference and
build up to FEM maybe? Not sure.
> On Feb 18, 2022, at 18:58, Matthew Knepley wrote:
>
> Should we put those back up?
>
> Thanks,
>
> Matt
>
> O
That was an early version of the new docs. Patrick, Hannah, Hong and I wrote
those tutorials as we were testing out the new format. The QuickStart tutorial
made it into the final set pretty much unchanged, but not sure if the rest of
the sections did.
> On Feb 18, 2022, at 15:23, Matthew
New code can (and absolutely should) use it right away, PetscDeviceContext has
been fully functional since its merger. Remember though that it works on a
“principled parallelism” model; the caller is responsible for proper
serialization.
Existing code? Not so much. In broad strokes the
happen as direct arguments to the function:
```
cublasXaxpy_petsc(RAII_xfer_to_device(),…);
```
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jan 23, 2022, at 21:37, Barry Smith wrote:
>
>
>
>> On Jan 23, 2022, at 10:01 PM, Junchao Zhang > <
of
cuda/hipDeviceProp)
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jan 22, 2022, at 12:55, Barry Smith wrote:
>
>
> I suggested years ago that -log_view automatically print useful information
> about the GPU setup (when GPUs are used) but eve
Is share/petsc/Makefile.user what you are looking for?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jan 13, 2022, at 21:49, Barry Smith wrote:
>
>
> https://petsc.org/release/docs/manual/getting_started/?highlight=user%20makefile
>
> <http
s the random CI failures due to out of memory!
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jan 8, 2022, at 13:36, Zhang, Hong wrote:
>
> Here is an interesting thread discussing the memory issue for PyTorch (which
> I think is also relevant to PETSc):
MB seems ludicrous. CUDA maintains a persistent pool of
streams that is not freed until cudaDeviceReset() is called. Maybe they
initialize this pool immediately on start-up of the context? AFAIK there is no
way to disable or modify this behavior.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - b
> They had no influence to the memory usage.
???
Comment out the ierr = _devices[id]->initialize();CHKERRQ(ierr); on line 360 in
cupmdevice.cxx as well.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh -
bjects/device/impls/cupm/cupmdevice.cxx:327 [ierr =
_devices[_defaultDevice]->configure();CHKERRQ(ierr);]
Comment this out
3. src/sys/objects/device/impls/cupm/cupmdevice.cxx:326 [ierr =
_devices[_defaultDevice]->initialize();CHKERRQ(ierr);]
Comment this out
Best regards,
Jacob Faibussowitsc
I hate C++ where huge chunks of real code are in header files.
Not quite, you will need to comment out
ierr = __initialize(dctx->device->deviceId,dci);CHKERRQ(ierr);
In src/sys/objects/device/impls/cupm/cupmcontext.hpp:202
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
:398
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jan 7, 2022, at 11:29, Jacob Faibussowitsch wrote:
>
>> You need to go into the PetscInitialize() routine find where it loads the
>> cublas and cusolve and comment out those lines then run wit
ierr =
PetscDeviceInitializeFromOptions_Internal(PETSC_COMM_WORLD);CHKERRQ(ierr);
#endif
At src/sys/objects/pinit.c:956
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Jan 7, 2022, at 11:24, Barry Smith wrote:
>
>
> Without log_view it does not load any cuBLAS/cuSolve immediately with
> -
> And your algorithm looks idempotent to me
Believe me, I was sufficiently shocked when everything magically started
working the 3rd time around :)
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Dec 8, 2021, at 09:29, Mark Adams wrote:
>
> Thanks
t;
3.
https://stackoverflow.com/questions/58313047/cannot-compile-r-packages-with-c-code-after-updating-to-macos-catalina
If these help then you’re lucky I never clean out my “misc” bookmarks folder :)
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Dec 8, 2021, at 09:06, Ma
You aren’t by chance on Catalina are you?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Dec 8, 2021, at 08:49, Mark Adams wrote:
>
> I am failing on OSX with openmpi. Kokkos is failing to build.
> I seem to be using:
>
> (conda_env) 08:46 1
aware mpi checker. IIRC we discussed
removing this at some point? I think Stefano mentioned we now do this check at
configure time?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Nov 13, 2021, at 22:57, Junchao Zhang wrote:
>
>
>
>
> On Sat, Nov 13, 2021
that it made sense to wrap them, and is the man in the middle between direct
cuda/hip calls and higher-level PetscDevice/PetscDeviceContext API.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Nov 10, 2021, at 12:28, Justin Chang wrote:
>
> Jacob,
>
, but for concrete
examples see the jacobf/2021-10-21/veccupm-async branch for the WIP port of
VecSeq in src/vec/vec/impls/seq/seqcupm/veccupm.hpp.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Nov 10, 2021, at 11:50, Justin Chang wrote:
>
> Paul Bauman was also
https://gitlab.com/petsc/petsc/-/merge_requests/4512
<https://gitlab.com/petsc/petsc/-/merge_requests/4512>
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Nov 1, 2021, at 11:00, Barry Smith wrote:
>
>
>PETSc code could check for the envi
and use these flags instead of
setting the cuda env variables. (Btw, can you test that using
‘-device_enable_cuda none’ does not crash when setting CUDA_VISIBLE_DEVICES=-1?)
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Nov 1, 2021, at 10:09, Stefano Zampini wr
Alternatively, we could run dos2unix over all the tests during configure stage
and error if this makes a diff.
https://linux.die.net/man/1/dos2unix
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Oct 28, 2021, at 08:22, Jacob Faibussowitsch wrote:
>
> Fix i
Fix is trivial, we just need to replace ‘\n’ with os.linesep everywhere.
https://docs.python.org/3/library/os.html#os.linesep
<https://docs.python.org/3/library/os.html#os.linesep>
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Oct 28, 2021, at 08:12, Matthe
Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Oct 2, 2021, at 09:33, Jacob Faibussowitsch wrote:
>
> Unrelated to the below (still reading the configure.log) but it looks like
> there’s a bug in the cuda compiler search:
>
> TESTING: checkCUDACompiler from
> config.s
in/win32fe/nvcc...not
found
Unable to find programs ['nvcc'] providing listing of the specific search path
Warning accessing /usr/local/cuda/bin gives errors: can only concatenate
str (not "builtin_function_or_method") to str
Best regards,
Jacob Faibussowitsch
(Jacob Fai
. Petsc targets python 2.6 or lower and 3.4 or lower,
however your change would make python 3.5 the new minimum:
Minimum required versions: 3.5
Incompatible versions: 2
Target versions not met: 2.6-, 3.4-
ctrl-F for “3.5” will find the file and reason in the output.
Best regards,
Jacob
https://gitlab.com/petsc/petsc/-/merge_requests/4284
<https://gitlab.com/petsc/petsc/-/merge_requests/4284>
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Sep 3, 2021, at 03:34, Stefano Zampini wrote:
>
> Jacob
>
> Just got a report
t and see if it works.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Aug 30, 2021, at 14:14, Mark Adams wrote:
>
> That did not seem to work.
>
> 15:09 main<> /gpfs/alpine/csc314/scratch/adams/petsc2$ mpicc --version
> gcc (GCC) 9.1.0
> Copyrig
Yeah I suppose so, all the values we alias are integral types so static const
should have equivalent compile-time assurance as constexpr.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Aug 30, 2021, at 13:44, Junchao Zhang wrote:
>
> Can you use less fanc
linked without a problem.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Aug 30, 2021, at 13:02, Jacob Faibussowitsch wrote:
>
>> No luck with C++14
>
> TL;DR: you need to have host and device compiler either both using c++17 or
> neither using c+
+17 onwards. Stupid, I know.
2. The linker (driven by the c++11/14 compiler since PETSc links using the host
compiler) comes along and now suddenly cannot find the literal definition,
because it doesn’t know what the c++17 did. Disaster!
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss -
s you to do, which is
strange. It just tells you about it. Googling it has not yielded useful info
either. Is this our own buggy code at fault or just an internal compiler
logging so rare that they forgot to turn it off?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Hello All,
All of our unit tests look for some kind of positive result, but is there any
established way in the harness to test for failure of a particular kind?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
a version of valgrind and I cannot recommend it enough. Not directly related
but it also comes with a suite of other useful gpu-related tools that catch
race conditions, uninitialized memory accesses and deadlocks.
https://docs.nvidia.com/cuda/cuda-memcheck/index.html
Best regards,
Jacob Faibus
Guess who’s back:
ld: warning: object file
(/Users/kongf/projects/petsc1/arch-darwin-c-opt/lib/libfblas.a(ddot.o)) was
built for newer OSX version (10.14) than being linked (10.9)
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On May 6, 2021, at 12:43, Fande K
is on face less code diff
and simpler to implement right now, it doesn’t fit with the single API doctrine.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Apr 27, 2021, at 09:33, Karl Rupp wrote:
>
> Hi,
>
> such adjustments should not need a direct modificati
Not out of the box no. There is -info ::self which makes info only print from
calls made on PETSC_COMM_SELF, but I don’t think that’s what you want. Best
advice would be to print to a file and grep the file for any lines starting
with the rank number you want.
Best regards,
Jacob
petsc, but they both share the
same .git folder (I think).
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Apr 17, 2021, at 17:24, Barry Smith wrote:
>
>
> Say I have a project (a code whose source is not in the PETSc repository)
> that require
imization transformations (such as arbitrary branch predictions,
etc), then the compiler may or may not get around to determining whether this
value was initialized.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Apr 11, 2021, at 20:10, Mark
module
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 16, 2021, at 18:25, Barry Smith wrote:
>
>
>
>
>> On Mar 16, 2021, at 5:03 PM, Satish Balay wrote:
>>
>> On Tue, 16 Mar 2021, Barry Smith wrote:
>&g
it with my
auto type lookup.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 16, 2021, at 17:03, Satish Balay via petsc-dev
> wrote:
>
> On Tue, 16 Mar 2021, Barry Smith wrote:
>
>>
>> Jacob,
>>
>>
Satish your branch built successfully.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 16, 2021, at 16:37, Satish Balay wrote:
>
> hm - generatefortranstubs is not useful for the custom stubs.
>
> From them - I would:
> -
Alternatively generatefortranstubs can traipse through
src//f90-mod/petsc.h90 and look for type t
definitions and build a list of petsc types that way, but at that point we’re
halfway to writing our own compiler.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312
PetscErrorCode z
end subroutine PetscRandomDestroy
Requires an “import tPetscRandom”. Previously both of these had “import
petscsys” stuck in them.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 16, 2021, at 16:13, Satish Balay via petsc-
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 16, 2021, at 14:41, Barry Smith wrote:
>
>
> Satish,
>
>The import tIS might only work because the IS is already defined in the
> same file so the compiler can p
id solution. I think I can get the
import stuff to work reasonably well (a lot of the infrastructure to capture
types is already present in the current generatefortranstubs).
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 16, 2021, at 12:5
generators have any notion of types? Specifically types
that originate from petsc?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 16, 2021, at 11:11, Satish Balay wrote:
>
> On Tue, 16 Mar 2021, Jacob Faibussowitsch wrote:
>
>>>
also shortens the compile time significantly.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 3, 2021, at 13:43, Satish Balay via petsc-dev
> wrote:
>
> The only change I can get working (i.e avoid compile errors) is to split
> p
This is certainly useful, prior to this I was using
git diff $(git merge-base --fork-point main)
To see branch changes (but this would dump all changes in all files in
terminal, so quite unwieldy for large diffs)...
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell
> 'gitk' is easier to read [for me] than 'git log --graph'
Where was this my entire life… best kept git secret!
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 3, 2021, at 13:55, Satish Balay wrote:
>
> 'gitk' is easier to read [
> git: 'graph' is not a git command. See 'git --help'.
I have it as an alias:
graph = !git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset
%s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative
Best regards,
Jacob Faibussowitsch
(Jacob Fai - b
I suppose we can run it through CI, see if it breaks?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 3, 2021, at 12:49, Satish Balay wrote:
>
> On Wed, 3 Mar 2021, Jacob Faibussowitsch wrote:
>
>> Hello All,
>>
>>
Interface
> Subroutine VecRestoreArrayReadF90(v,array,ierr)
> import tVec
> implicit none
> real(kind=selected_real_kind(10)), pointer :: array(:)
> integer(kind=selected_int_kind(5)) ierr
> type(tVec) v
> E
base, you can pick an N such that you only get
your commits from the branch.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 2, 2021, at 22:02, Barry Smith wrote:
>
>
>
>> On Mar 2, 2021, at 9:24 PM, Mark Adams > &
Alternatively have configure recognize the “+=“ operator?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Mar 1, 2021, at 13:39, Satish Balay wrote:
>
> Yeah - we don't have the 'add-to-defaults' feature. Currently its either 'use
&
configure once, copy the
CFLAGS, and reconfigure with my flags added to the end of the list.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
Yes, this also seems to work on my end.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Feb 15, 2021, at 12:05, Satish Balay wrote:
>
> Does setting MACOSX_DEPLOYMENT_TARGET also work?
>
> Satish
>
> On Mon, 15 Feb 2021,
).
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Feb 15, 2021, at 11:46, Jacob Faibussowitsch wrote:
>
> Ok so if I pass -mmacosx-version-min=11.2 to the linker the warning
> disappears...
>
> Best regards,
>
> Jacob Faibusso
Ok so if I pass -mmacosx-version-min=11.2 to the linker the warning
disappears...
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Feb 15, 2021, at 11:41, Jacob Faibussowitsch wrote:
>
> I can reproduce the warning compiling just that si
f ./build
And error:
ld: warning: object file (./build/conftest.o) was built for newer macOS version
(11.2) than being linked (11.0)
Note I recently uninstalled and reinstalled command line tools too, which does
not seem to have fixed it.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss
gt;
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Feb 14, 2021, at 17:07, Jed Brown wrote:
>
> Barry Smith writes:
>
>>> On Feb 14, 2021, at 12:13 PM, Jed Brown wrote:
>>>
>>> Barry Smith writes:
> In other words, everything is doable until you encounter an error. Very clear.
Ah yes, the Wile E. Coyote method of programming, as long as you don’t look
down there’s nothing to stop you running on thin air…
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312)
--with-threadsafty=1
Spelling?
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: +1 (312) 694-3391
> On Jan 16, 2021, at 12:16, Mark Adams wrote:
>
>
> I don't seem to bet getting PETSC_HAVE_THREADSAFTY getting define here. I am
> not seeing a
t;https://github.com/kokkos/kokkos/wiki/Kokkos::ExecutionSpaceConcept>
https://github.com/kokkos/kokkos/wiki/Kokkos%3A%3ACuda
<https://github.com/kokkos/kokkos/wiki/Kokkos::Cuda> <—— cuda specific
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3
t regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Jan 11, 2021, at 08:14, Mark Adams wrote:
>
> Ah, so first first maybe the Solver does not need a stream because it uses
> VecScatter ?
>
> The model is 1) block to get your data, 2) doi
, but admittedly this was a
while back.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Jan 10, 2021, at 13:10, Mark Adams wrote:
>
>
>
> On Sat, Jan 9, 2021 at 7:37 PM Jacob Faibussowitsch <mailto:jacob@gmail.com>> wrote:
It is a single object that holds a pointer to every stream implementation and
toggleable type so it can be universally passed around. Currently has a
cudaStream and a hipStream but this is easily extendable to any other stream
implementation.
Best regards,
Jacob Faibussowitsch
(Jacob Fai
lt;https://gitlab.com/Jfaibussowitsch> ago”
And just manually scroll through it.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Jan 9, 2021, at 16:22, Barry Smith wrote:
>
>
> For unresolved threads you can press the arrow in
at either MR, it
would be very useful to get your input, as tailoring either of these approaches
for pipelined algorithms is key.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Jan 9, 2021, at 15:01, Mark Adams wrote:
>
> I would like to
> Should I make a MR to release with this addition?
It is already in master, doesn’t release get synchronized with master every so
often like maint was? If not, then yes release will need its own MR with the
fix.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (
Although if you temporarily want to patch it in, just slap
bibtex_bibfiles = ['../tex/petsc.bib','../tex/petscapp.bib’]
Anywhere in conf.py
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Dec 26, 2020, at 12:27, Jacob Faibussowitsch wrote:
>
I looks like release does not yet have the fix from master (arguably the fix
should have gone to release anyways…)
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Dec 26, 2020, at 12:05, Barry Smith wrote:
>
>
> I was trying to bu
Barry,
What branch are you on? This should have been fixed by
https://gitlab.com/petsc/petsc/-/merge_requests/3479
<https://gitlab.com/petsc/petsc/-/merge_requests/3479>, try rebasing over
master.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 69
/408999/gfortran-compiler-error-on-mac-os-big-sur
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
VCC=11.1.1
+ exec /usr/tce/packages/cuda/cuda-11.1.1/nvidia/bin/nvcc -std=c++14 -Xlinker
'"-rpath=/usr/tce/packages/cuda/cuda-11.1.1/nvidia/lib64:/usr/tce/packages/cuda/cuda-11.1.1"'
nvcc fatal : No input files specified; use option --help for more information
Best regards,
Jacob F
is happening
right now, although maybe Satish will know better.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Dec 6, 2020, at 15:30, Mark Adams wrote:
>
> This is the status after the first fail. I have nothing to do with these
to resolve them. If this is the case then when the
rebase fails at some commit some of the files will be staged with the changes
from both commits that you must __manually__ reconcile.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Dec 6, 2020, at 14
DA I believe the tool is nvidia-smi. Should make sure this automatic
detection works when configuring —with-batch though since login nodes might
have different arch than compute.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Sep 25, 2020, at 21:
environment I can definitely appreciate
that users are rightfully distrustful of yet another data collection request,
but if it is transparent and un-intrusive enough it may be palatable.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Cell: (312) 694-3391
> On Sep 14, 2020, at
1 - 100 of 161 matches
Mail list logo
