This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/42568] [Cygwin] BLOCKDATA referenced in EXTERNAL not loading from library
- From: "jvdelisle at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 5 Jan 2010 03:01:21 -0000
- Subject: [Bug fortran/42568] [Cygwin] BLOCKDATA referenced in EXTERNAL not loading from library
- References: <bug-42568-18131@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #20 from jvdelisle at gcc dot gnu dot org 2010-01-05 03:01 -------
I have read through the links given by Dave. My take is that we have some
implementation dependent, non portable, behaviour in linkers. Now that we know
we have this inconsistency, the question is do we want to fix this with a work
around in gfortran?
>From my read, there are situations where this is not desired behaviour.
Obviously linux/Gnu is doing it. If so, exactly how is this done? Should it be
handled by Cygwin? (by the linker?)
Dave, do you know how to emit the forceload and just exactly what is this?
What to do? and who?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42568