Re: [petsc-dev] CI error

https://gitlab.com/petsc/petsc/-/merge_requests/3865 Satish On Tue, 13 Apr 2021, Satish Balay via petsc-dev wrote: > gcc-11 is giving a bunch of warnings - have to go through them and see if > they are fixable.. > [its not in CI] > > Satish > > On Mon, 12 Apr 2021, Barry Smith wrote: > > >

Re: [petsc-dev] CI error

Why bother reading the standard when you are hacking on compiler code, your intuition is better anyways :-). > On Apr 13, 2021, at 9:46 AM, Lawrence Mitchell wrote: > > > >> On 13 Apr 2021, at 05:21, Barry Smith wrote: >> >> >> https://stackoverflow.com/questions/201101/how-to-init

Re: [petsc-dev] CI error

> On 13 Apr 2021, at 05:21, Barry Smith wrote: > > > https://stackoverflow.com/questions/201101/how-to-initialize-all-members-of-an-array-to-the-same-value > seems to indicate one can initialize all entries in C with one {0} but who > trusts the web or all compilers. > > Have you tr

Re: [petsc-dev] CI error

On Tue, Apr 13, 2021 at 12:21 AM Barry Smith wrote: > > I like the diversity of slightly different test boxes. If all test boxes > are the same than that limits what variants we test and reduces the > usefulness of the CI; since users will face this diversity in their > machines and end up with

Re: [petsc-dev] CI error

Yes, this is annoying and frustrating for us to have deal with this kind of thing, but imagine how annoying and frustrating it is for an average user who has 1/100th the HPC experience we do. This is why I like to have these fully resolved at the library level; yes it is more work for us; but

Re: [petsc-dev] CI error

I like the diversity of slightly different test boxes. If all test boxes are the same than that limits what variants we test and reduces the usefulness of the CI; since users will face this diversity in their machines and end up with errors we never see before hand (which is bad). This ki

Re: [petsc-dev] CI error

This job gets run on either pj01 or pj02 - each have slightly different version of gcc. (and they behave differently wrt certain warnings) [trade-off with diversity in testing and having redundancy in available work machines - so jobs are not stuck on a single box] I guess I should somehow fi

Re: [petsc-dev] CI error

rom: petsc-dev <mailto:petsc-dev-boun...@mcs.anl.gov>> On Behalf Of Barry Smith > Sent: Sunday, April 11, 2021 17:51 > To: Mark Adams mailto:mfad...@lbl.gov>> > Cc: For users of the development version of PETSc <mailto:petsc-dev@mcs.anl.gov>> > Subject: Re: [

Re: [petsc-dev] CI error

ent: Sunday, April 11, 2021 17:51 > To: Mark Adams mailto:mfad...@lbl.gov>> > Cc: For users of the development version of PETSc <mailto:petsc-dev@mcs.anl.gov>> > Subject: Re: [petsc-dev] CI error > > > > > > You might be able to do: > >

Re: [petsc-dev] CI error

> (Jacob Fai - booss - oh - vitch) > > Cell: (312) 694-3391 > > > > *From:* petsc-dev *On Behalf Of *Barry > Smith > *Sent:* Sunday, April 11, 2021 17:51 > *To:* Mark Adams > *Cc:* For users of the development version of PETSc > > *Subject:* Re: [petsc-dev] CI e

Re: [petsc-dev] CI error

users of the development version of PETSc Subject: Re: [petsc-dev] CI error You might be able to do: col_scale[LANDAU_MAX_Q_FACE = {0}; but then the compiler may complain about not initializing enough values. Googling this type of initialization might help, something C initialize

Re: [petsc-dev] CI error

You might be able to do: > col_scale[LANDAU_MAX_Q_FACE = {0}; but then the compiler may complain about not initializing enough values. Googling this type of initialization might help, something C initialize arrays "may be used uninitialized" > On Apr 11, 2021, at 2:05 PM, Mark Adams wrot

Re: [petsc-dev] CI error

This warning went away. i don't know why. On Sun, Apr 11, 2021 at 2:10 PM Mark Adams wrote: > I get this error in CI with complex float: > https://gitlab.com/petsc/petsc/-/jobs/1170144554 > > I put in code earlier to fix this warning about uninitialized vars, but > now it does not seem to work:

[petsc-dev] CI error

I get this error in CI with complex float: https://gitlab.com/petsc/petsc/-/jobs/1170144554 I put in code earlier to fix this warning about uninitialized vars, but now it does not seem to work: /home/glci/builds-stage1/AbTGp5-t/0/petsc/petsc/src/ts/utils/dmplexlandau/plexland.c:414:94: error: ‘co

[petsc-dev] CI error with OMP code - sycl problem?

I get this error with omp but it looks fine to me. I see its from a (new) sycl test. Is this a bug? /home/glci/builds/dDpd88Yu/0/petsc/petsc/src/dm/impls/plex/landau/plexland.c(1455): error #3180: unrecognized OpenMP #pragma 1781 #pragma omp