On Wed, May 2, 2018 at 1:14 PM, Jed Brown <j...@jedbrown.org> wrote: > Matthew Knepley <knep...@gmail.com> writes: > > > On Wed, May 2, 2018 at 12:15 PM, Jed Brown <j...@jedbrown.org> wrote: > > > >> Lisandro Dalcin <dalc...@gmail.com> writes: > >> > >> > On Wed, 2 May 2018 at 17:29, Satish Balay <ba...@mcs.anl.gov> wrote: > >> > > >> >> So we need a 64bit arm with gcc8 - for this testcase failure? > >> > > >> > > >> > Or a big-endian machine/OS ? > >> > >> Shouldn't be necessary, but why are we so concerned about making a test > >> case fail instead of implementing correct behavior? > >> > > > > How would you know your fix was correct? > > Documentation and/or reading assembly.
Its good that tests are superfluous for code you write because it conforms to standards and you check the assembly. We should take out all the SF tests. That would decrease runtime. Matt > I don't have gfortran-8 > installed yet, but Satish says he does so I offered a tiny snippet that > can be used to confirm that the documentation isn't lying. If you > really care to make code crash, we can do that too (as I described). > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener https://www.cse.buffalo.edu/~knepley/ <http://www.caam.rice.edu/~mk51/>
