public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42568] [Cygwin] BLOCKDATA referenced in EXTERNAL not loading from library
Date: Mon, 04 Jan 2010 18:05:00 -0000 [thread overview]
Message-ID: <20100104180542.10830.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42568-18131@http.gcc.gnu.org/bugzilla/>
------- Comment #17 from davek at gcc dot gnu dot org 2010-01-04 18:05 -------
(In reply to comment #16)
> You made an unmerited assertion that "COMMON symbols don't cause
> members to be pulled in from library archives." I've shown the
> counter example.
On what platform?
> This appears to be linker issue on cygwin.
It appears to be the entirely correct behaviour of the linker on PE-COFF
platforms; I don't know about ELF platforms, which may well behave differently.
Why do you supposed the "forceload" mechanism existed in g77 if not to allow
the compiler to generate code that worked regardless of the target object
format?
See here: http://www.airs.com/blog/archives/48
>"In general the linker will not include archives if they provide a definition for a common symbol."
Isn't that what's going on here?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42568
next prev parent reply other threads:[~2010-01-04 18:05 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 23:06 [Bug fortran/42568] New: " urbanjost at comcast dot net
2010-01-01 0:46 ` [Bug fortran/42568] " kargl at gcc dot gnu dot org
2010-01-01 1:57 ` urbanjost at comcast dot net
2010-01-01 2:50 ` kargl at gcc dot gnu dot org
2010-01-01 6:23 ` jvdelisle at gcc dot gnu dot org
2010-01-01 6:36 ` jvdelisle at gcc dot gnu dot org
2010-01-02 7:50 ` urbanjost at comcast dot net
2010-01-04 3:25 ` jvdelisle at gcc dot gnu dot org
2010-01-04 3:40 ` jvdelisle at gcc dot gnu dot org
2010-01-04 3:52 ` jvdelisle at gcc dot gnu dot org
2010-01-04 9:44 ` [Bug fortran/42568] [Cygwin] " burnus at gcc dot gnu dot org
2010-01-04 15:43 ` davek at gcc dot gnu dot org
2010-01-04 16:06 ` dominiq at lps dot ens dot fr
2010-01-04 16:13 ` kargl at gcc dot gnu dot org
2010-01-04 16:36 ` davek at gcc dot gnu dot org
2010-01-04 17:14 ` kargl at gcc dot gnu dot org
2010-01-04 18:05 ` davek at gcc dot gnu dot org [this message]
2010-01-04 18:06 ` davek at gcc dot gnu dot org
2010-01-04 18:57 ` kargl at gcc dot gnu dot org
2010-01-05 3:01 ` jvdelisle at gcc dot gnu dot org
2010-01-05 14:46 ` burnus at gcc dot gnu dot org
2010-01-05 16:10 ` ian at airs dot com
2010-01-05 18:13 ` dominiq at lps dot ens dot fr
2010-01-16 23:18 ` kargl at gcc dot gnu dot org
2010-01-16 23:47 ` kargl at gcc dot gnu dot org
[not found] <bug-42568-4@http.gcc.gnu.org/bugzilla/>
2014-01-13 13:40 ` dominiq at lps dot ens.fr
2015-09-05 10:42 ` dominiq at lps dot ens.fr
2015-09-15 5:31 ` urbanjost at comcast dot net
2015-09-18 16:57 ` jvdelisle at gcc dot gnu.org
2017-08-15 14:29 ` urbanjost at comcast dot net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100104180542.10830.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).