search

jabbaqin / p3dfft

Automatically exported from code.google.com/p/p3dfft
GNU General Public License v3.0
0 stars 0 forks source link

Problems with name mangling in module functions #58

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
As p3dfft is Fortran module, the names in the object file may have different 
names depending on the compiler. This is so far resolved by using 
compiler-specific FORT_MOD_NAME macros.

Actually this is not viable solution for the Cray and SUN compilers. They use, 
well, weird object names for Fortran module functions, which are unusuable in 
C++-code. The best solution for this problem (at least for the SUN and Cray 
compiler) is the use of the BIND-directive with module function definition. 
This would allow the use of a compiler independet object name. I am not 
completely sure if this a general feature shared by all Fortran compilers. If 
so I would suggest using the bind command rather than using FORT_MOD_NAME macro.

Original issue reported on code.google.com by sla...@astro.uni-wuerzburg.de on 7 Mar 2011 at 11:04

GoogleCodeExporter commented 9 years ago 
Done

Original comment by dmitry...@gmail.com on 16 Mar 2015 at 11:57

GoogleCodeExporter commented 9 years ago

Original comment by dmitry...@gmail.com on 17 Mar 2015 at 12:02