[Bug fortran/33647] New: _gfortran_copy_string missing in libgfortran.a

[Bug fortran/33647] New: _gfortran_copy_string missing in libgfortran.a

[longb at cray dot com]

In the library .../lib64/libgfortran.a, the 4.1.2 version has a routine

  _gfortran_copy_string

in the strong_intrinsics.o component.  For the same 4.2.1 library there is no
corresponding entry point.

It appears that codes compiled with 4.1.2 generate internal calls to this entry
point.  Attempting to link a library built with 4.1.2 and a code compiled and
linked with the 4.2.1 compiler results in an "undefined reference" message from
the loader for _gfortran_copy_string.

Is it by design that codes compiled with 4.1.2 cannot be linked with 4.2.1? Is
it a viable workaround to manually extract the string_intrinsic.o component
from the old libgfortran.a file and insert it into the new libgfortran.a
library, replacing the current version?


-- 
           Summary: _gfortran_copy_string missing in libgfortran.a
           Product: gcc
           Version: 4.2.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: longb at cray dot com
 GCC build triplet: x86_64-suse-linux
  GCC host triplet: x86_64-suse-linux
GCC target triplet: x86_64-suse-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33647

[Bug fortran/33647] _gfortran_copy_string missing in libgfortran.a

[pinskia at gcc dot gnu dot org]

------- Comment #1 from pinskia at gcc dot gnu dot org  2007-10-03 19:22 -------
And this is by design.  gfortran 4.1 is ABI incompatiable with gfortran 4.2. 
This is one of the reasons why in 4.2 (or is it only on the trunk), we added
symbol versioning support.  This is not the only place where 4.1 is different
from 4.2.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33647

[Bug fortran/33647] _gfortran_copy_string missing in libgfortran.a

[longb at cray dot com]

------- Comment #2 from longb at cray dot com  2007-10-03 19:44 -------
Subject: Re:  _gfortran_copy_string missing in libgfortran.a

I suspected this might be the case, but did not find it documented.  
Thanks for the quick reply.

Cheers,
Bill


pinskia at gcc dot gnu dot org wrote:
> ------- Comment #1 from pinskia at gcc dot gnu dot org  2007-10-03 19:22 -------
> And this is by design.  gfortran 4.1 is ABI incompatiable with gfortran 4.2. 
> This is one of the reasons why in 4.2 (or is it only on the trunk), we added
> symbol versioning support.  This is not the only place where 4.1 is different
> from 4.2.
>
>
>   


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33647