Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | FortranCInterface: Fix mangling detection with Cray Fortran >= 7.3.2 | Brad King | 2011-03-24 | 1 | -7/+0 |
| | | | | | | | | | | | | | | | The Cray Fortran compiler started using module init symbols in version 7.3.2. Starting in commit 71287734 (Teach FortranC interface for Intel, PGI, and gcc 4.2, 2009-08-05) we provide C versions of the module init symbols so that the detection executable can link when the C versions of the module-mangled symbols are picked up. If no C module-mangled symbol matches then we cannot let the C module init symbol appear because it will be duplicated by the Fortran copy that provides the module-mangled symbol. This was first handled for the PathScale compiler in commit 21faaa5d (FortranCInterface: Fix PathScale detection, 2010-01-22) and commit 46858720 (FortranCInterface: Fix PathScale detection again, 2010-02-16). Handle it now for the Cray compiler too. | ||||
* | FortranCInterface: Fix PathScale detection | Brad King | 2010-01-22 | 1 | -0/+6 |
| | | | | | | | PathScale Fortran mangles module symbols as "MYSUB.in.MYMODULE" and also requires "mymodule_" when the module is imported. We cannot provide the symbol with ".in." mangling so we should not provide "mymodule_" because it would duplicate the one in the Fortran-provided object file. | ||||
* | Cleanup FortranCInterface for PGI and GCC 4.2 | Brad King | 2009-08-05 | 1 | -1/+2 |
| | | | | | This documents the purpose of the extra my_module_.c and mymodule.c source files, and sorts the symbols. | ||||
* | Teach FortranC interface for Intel, PGI, and gcc 4.2 | Bill Hoffman | 2009-08-05 | 1 | -0/+1 |