I just want to future-proof things as
much as possible without having to rewrite the entire Fortran <-> C
interface.)
Thanks...
-Bob
Bob Deen @ NASA-JPL Multmission Image Processing Lab
bob.d...@jpl.nasa.gov
On 1/3/18 11:43 AM, Janne Blomqvist wrote:
On Wed, Jan 3, 2018 at 8:34 PM, Bob Deen wrote:
On 12/29/17 5:31 AM, Janne Blomqvist wrote:
In order to handle large character lengths on (L)LP64 targets, switch
the GFortran character length from an int to a size_t.
This is an ABI change, as
case for strings > 2 GB that justifies the breakage? I
certainly understand wanting to do it "right" but I'm probably not the only one
with practical considerations that argue against it if there are no compelling
use cases.
Thanks...
-Bob
Bob Deen @ NASA-JPL Multimission Image Processing Lab
bob.d...@jpl.nasa.gov
L Multimission Image Processing Lab
bob.d...@jpl.nasa.gov
On 12/12/16 10:26 AM, Bob Deen wrote:
However, this will also affect people doing C->Fortran calls the
old-fashioned way without ISO_C_BINDING, as they will have to change
the string length argument from int to size_t in their protot
On 12/19/16 11:33 AM, Janne Blomqvist wrote:
On Mon, Dec 19, 2016 at 6:43 PM, Bob Deen wrote:
Hi all...
I never saw any followup on this...?
It's one thing to break the ABI between the compiler and the gfortran
library; those can generally be expected to be in sync. It's anothe
n any case). Unless I'm misunderstanding the application of the
issue?
Would it be possible for you to try my test case again after this patch,
just to make sure? I can post it again if you like.
Thanks...
-Bob
Bob Deen @ NASA-JPL Multimission Image Processing Lab
bob.d...@jpl.nasa.gov
On
wonder if we shouldn't exorcise all the varargs stuff, it seems to
cause more problems than benefits? But not in stage4 if we can avoid
it..
Please don't. Some of us still use varargs interfaces (in my case,
Fortran calling C stdarg subroutines).
Thanks...
-Bob Deen @ NASA-JP
On 2/19/19 2:44 PM, Thomas Koenig wrote:
Bob,
Some of us still use varargs interfaces (in my case, Fortran calling C
stdarg subroutines).
The problem for us is that that sometimes using varargs made standard-
conforming Fortran code like, in file a.f
subroutine foo(a)
print *
