Re: [petsc-dev] 32 bit compilers and PETSc

Not really bad compilers. Just 32 bit compilers. 640k is all anyone will ever need. > On Mar 4, 2021, at 10:13 AM, Scott Kruger wrote: > > On 2021-03-04 08:58, Satish Balay via petsc-dev did write: >> On Wed, 3 Mar 2021, Barry Smith wrote: >>> >>> Can we make ./configure ban 32 bit

[petsc-dev] Solaris 64 bit problems building PETSc

Any idea how to fix this stuff or just toss Solaris? https://gitlab.com/petsc/petsc/-/jobs/1071928836 ld: warning: relocation error: R_AMD64_PC32: file

[petsc-dev] petsc-3.14.5 now available

Dear PETSc users, The patch release petsc-3.14.5 is now available for download. http://www.mcs.anl.gov/petsc/download/index.html Satish

Re: [petsc-dev] 32 bit compilers and PETSc

On 2021-03-04 08:58, Satish Balay via petsc-dev did write: > On Wed, 3 Mar 2021, Barry Smith wrote: > > > >Can we make ./configure ban 32 bit compilers unless a special flag is > > used? And just have one CI test that uses 32 bit where we turn off examples > > that overflow 32 bits? > > We

Re: [petsc-dev] Commit squashing in MR

If you're in Emacs, Magit (https://github.com/magit/magit) is excellent for much the same things, and works over remote (i.e., I'm editing "ssh:thathost:path/to/file.c" and invoke magit). There's also a (partial) magit clone for vscode.

Re: [petsc-dev] 32 bit compilers and PETSc

On Wed, 3 Mar 2021, Barry Smith wrote: > >I just wasted an enormous amount of time "debugging"my additions to BAIJ > on the solaris test machines. Turns out there was no bug at all just that the > compilers default to 32 bit and we have no possible way of detecting size_t > overflow; so

Re: [petsc-dev] Commit squashing in MR

I have also been enjoying using lazygit (thanks, Lisandro, for the tip!). It's a similar sort of thing but runs in the terminal. I find it very useful for those things where the command line git tool falls down (staging parts of files, browsing large sets of changes), and I like that I don't