From: hjl@nynexst.com (H.J. Lu)
To: ian@cygnus.com (Ian Lance Taylor)
Cc: gas2@cygnus.com
Subject: Re: An ld bug?
Date: Tue, 03 Oct 1995 08:20:00 -0000 [thread overview]
Message-ID: <9510031520.AA26422@nynexst.com> (raw)
In-Reply-To: <199510031425.KAA23139@sanguine.cygnus.com>
>
> From: hjl@nynexst.com (H.J. Lu)
>
> It seems gas-950822 doesn't treat common symbols right. Does the newer
> snapshot still have this bug? BTW, I tested it under i486-linux.
>
> It only takes you a minute to note what you think is incorrect about
> the program. Please do that, rather than making me figure out what
> the problem is. Thanks.
Sorry for that.
>
> In this case, I assume that you think that the common symbol in the
> object file should cause the object in the archive to be brought in.
> That's the way in works in a.out, but it is not the way it works in
> ELF. In ELF, objects are only brought in from archives to fill
> references by undefined symbols.
>
> However, interestingly, I tested the program on Irix 5, UnixWare, and
> Solaris, and, on Solaris, it works the way it does in a.out. I assume
> this is for SunOS compatibility. It happens to contradict the Solaris
> linker documentation: ``For an archive library, only those routines
> defining an unresolved external reference are loaded.''
>
From my Solaris 2.3 linker manual, on page 12 regarding "Archive
Processing", it says the link-editor will extract a relocatable object
from an archive if it contains a data symbol definition that
satisfies a common symbol definition.
I think that makes sense. Maybe it has been changed in Solaris 2.4/2.5.
Thanks.
--
H.J. Lu
NYNEX Science and Technology, Inc. hjl@nynexst.com
next prev parent reply other threads:[~1995-10-03 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-10-02 21:00 H.J. Lu
1995-10-03 7:25 ` Ian Lance Taylor
1995-10-03 8:20 ` H.J. Lu [this message]
1995-10-03 8:43 ` David S. Miller
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=9510031520.AA26422@nynexst.com \
--to=hjl@nynexst.com \
--cc=gas2@cygnus.com \
--cc=ian@cygnus.com \
/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).