08-17-2020, 01:20 PM
(08-14-2020, 11:15 PM)ceanwang Wrote: I have a version which includes BANDIT. Got the exe, but has problem to run.Talked with Bill. Need a bit fine turn of the order.
Glad you have a runable exe.
Edit:
I tried to compile with your script under windows. The exe still has problem to run. Could you solve the all-elem-test. dat case?
This is most weird. I managed to run that test case under Linux with my binary, and under Windows with the publicly-released binary, but the one I compiled was no good, there's some error being raised in the output functions.
I attached all input and output data and files from the three runs (public Windows binary, CMake Windows binary, and CMake Linux binary).
Okay so... I have some points I think we should keep in mind while investigating this.
- GNU gfortran is a rather consistent compiler for F90/F95, so this being a gfortran bug is unlikely, but not impossible.
- Can we guarantee the same source code used for the public EXE is the same as git latest's? If not, this might have been introduced in the meantime.
- The fact the exact same source code produces different behavior should trace this error back to the OS-specific files, but none of them are tied to output formatting AFAIK, so this is a bit concerning indeed.
- Thanks to some random glitch in MinGW, I can't get a proper backtrace of the error, all we know is it was raised in the BANDIT_MODULE.f file, line 677 (see the output files (stdout/stderr will be of most help) for details)
- I do not think this has anything to do with the compilation order/process, as it would've probably caused a link-time diagnostic messag...
- ...neither do I think this has anything to do with my only change to the READ_CL source code, since it does not have anything to do with formatted output.