[root]/branches/budaev/HEDG2_06_gprof2
Author | Changes | Lines of Code | Lines per Change |
---|---|---|---|
sbu062 | 16 (100.0%) | 147 (100.0%) | 9.1 |
deleted work branch: fixed intel compiler bug workaround for FUCK_IFORT_WA1 block
0 lines of code changed in 3 files:
fix notification on Windows
0 lines of code changed in 2 files:
more info describing intel compiler bug with segmentation fault as workaround code in r7734
9 lines of code changed in 1 file:
added workarounds against intel fortran compiler bugs that apear in optimised binary builds with O3, components of derived types and getters from different modules become unaccessible and result in segmentation crashes
22 lines of code changed in 1 file:
print sanitiser bounds to log at start
2 lines of code changed in 1 file:
doc: description for sanitiser bounds
5 lines of code changed in 1 file:
global validation, low and high,parameters in (sanitise) and (do_sanitise)
7 lines of code changed in 1 file:
refactored sanitise functions: (do_sanitise) and (sanitise), the former calling IEEE math modules
102 lines of code changed in 2 files:
fix ifort crashes: got rid of FILE_IO object as it breaks ifort; use array sanitizer in (generation_stats_record_write) to avoid crashes in csv file
When using a very long history, some perception object history stack values are broken/uninitialised/invalid which breaks output in CSV_IO call, hence use sanitiser added in r7727. Switched to raw CSV_IO calls instead of the FILE_IO wrapper because intel ifort breaks public file handle object rendering file unit and name unaccessible. Debugging did not succeed, perhaps it's a bug in Intel compiler. So, raw CSV_IO calls are used, but they are not verbose. Actually, FILE_IO may be oblivious...
0 lines of code changed in 2 files:
fix ifort crashes: initial implementation of data sanitiser
0 lines of code changed in 2 files: