kraused / pvo Goto Github PK

View Code? Open in Web Editor NEW

2.0 2.0 1.0 320 KB

Parallel VTK Output Library

License: Other

Shell 1.17% Fortran 19.63% C 53.66% C++ 25.54%

pvo's People

Stargazers

Watchers

Forkers

sspeng

pvo's Issues

XLF on BG/Q does not mangle Fortran names

PVO does not compile on BlueGene/Q since we use the same names for C and Fortran subroutines. This works find on systems where Fortran names are mangled (e.g., by adding an underscore). However, the XLF compiler does so only when given the flag "-qextname".

One option to cope with this issue would be to make the language part of the symbol name. NetCDF uses this approach by prefexing C routines with nc_, Fortran 70 routines by nf_ and Fortran 90 by nf90_.

On BG/Q code is stored in the data section

The fname.sh assumes that the "pvo_symbol" symbol is placed in the text section ("T") but xlf places it in the data section ("D"). This makes the fname.sh script fail.

PVO should allow to provide an alloc function

Similar to Lua we should take a pvo_Alloc function for handling memory allocations.

Compiler flags not passed to fname.sh

On BlueGene/Q we need to pass "-qextname" to the fortran compiler. This can be achieved by adding -DCMAKE_Fortran_FLAGS-"-qextname" to the cmake invocation but these flags are not passed to the fname.sh.