| 1 |
cfortran (4.4-10) unstable; urgency=low |
| 2 |
|
| 3 |
cfortran.h has been enhanced to support the gfortran compiler. Use the |
| 4 |
flag -DgFortran to your C/C++ compiler, or #define gFortran somewhere in |
| 5 |
your source code above the #include <cfortran.h>. Doing this is also |
| 6 |
likely necessary if you use g77 with the -fno-f2c flag, or f2c with the |
| 7 |
-R flag. |
| 8 |
|
| 9 |
-- Kevin B. McCarty <[email protected]> Wed, 5 Apr 2006 12:56:15 -0400 |
| 10 |
|
| 11 |
cfortran (4.4-8) unstable; urgency=low |
| 12 |
|
| 13 |
In this version of cfortran, the header file cfortran.h has been improved, |
| 14 |
as planned by the original author, to enforce the fact that f2c and g77 |
| 15 |
generate code from FORTRAN REAL functions that returns a C "double". |
| 16 |
This should fix runtime breakage with cfortran on some platforms (e.g. |
| 17 |
AMD64); see for instance http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15397 |
| 18 |
|
| 19 |
If you create libraries that depend upon cfortran to build, it is possible |
| 20 |
that this change could affect the ABI of your library. Be particularly |
| 21 |
alert to this possibility if you use the PROTOCCALLSFFUN* and/or |
| 22 |
FCALLSCFUN* macros with the first argument to the macro(s) (i.e. the |
| 23 |
function return type) being "FLOAT". |
| 24 |
|
| 25 |
-- Kevin B. McCarty <[email protected]> Fri, 9 Dec 2005 17:49:46 -0500 |