public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: hjl@nynexst.com
Cc: gas2@cygnus.com
Subject: Re: An ELF linker bug?
Date: Mon, 11 Sep 1995 08:07:00 -0000	[thread overview]
Message-ID: <199509111507.LAA19337@sanguine.cygnus.com> (raw)
In-Reply-To: <m0srxk6-00011HC@didi.nynexst.com>

   From: hjl@nynexst.com (H.J. Lu)
   Date: Sun, 10 Sep 1995 21:33:01 -0400 (EDT)

   Here is a simple test. "f1" should print out "foo". Under UnixWare,
   it worked fine. But gas-950822 failed to pick up the strong "foo".
   Also Solaris 2.3 got it wrong.

I think this case is undefined.  You are defining a symbol twice in an
archive.  It does not matter that one definition is weak and one is
normal.  A weak definition is pulled in from an archive just as a
normal one is.  This case is equivalent to defining the same symbol in
two different object files and including them both in an archive: you
can not predict which object file will be included in the final link.

Ian


      reply	other threads:[~1995-09-11  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-09-10 18:33 H.J. Lu
1995-09-11  8:07 ` Ian Lance Taylor [this message]

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=199509111507.LAA19337@sanguine.cygnus.com \
    --to=ian@cygnus.com \
    --cc=gas2@cygnus.com \
    --cc=hjl@nynexst.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).