Closed gnikit closed 2 years ago
I did and I haven't seen any other issues, actually I config with -fcheck=all,no-array-temps
, which takes care of a few more things like pointers, mem allocation, out of bounds checks, etc. I agree it might be useful when debugging.
The only other thing that I would ideally add in this PR is to make all the regression tests use a relative path to fluidity/flredecomp instead of just calling fluidity i.e. ../../bin/fluidity
in place of fluidity
because testing between multiple versions of Fluidity becomes harder than it should be (IMO).
On this last comment, that could be easily done by adding replace
methods here.
@Patol75 you are right, I think it might be worth doing this in a separate PR to keep things tidy.
Might also be worth updating the .flml and .xml files with spud-update-options, replacing the XML comments with
Feel free to push commits to testharnessClean - the associated PR should hopefully be discussed again soon.
@stephankramer would you mind having one last look (I forgot to push a couple commits last time) so the review was auto-rejected.
While doing some work I encountered one more short-circuit evaluation in Sediments along with some compiler failures when enabling for using recursion in routines not marked as such (you can replicate the failures by turning -fcheck=recursion` on during compilation).
I also fixed some of the
clean
targets in our test Makefiles because they were polluting the git tree after running tests.Summary of changes
.gitignore
slightly more aggressive to specifically ignore all the configure and compile generated files and nothing moreI believe this is now done.