public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com
Subject: Re: Why does gas have both S_IS_EXTERNAL and S_IS_EXTERN?
Date: Wed, 20 Apr 2005 03:07:00 -0000	[thread overview]
Message-ID: <m33btmrvs7.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20050419191948.GB19412@lucon.org>

"H. J. Lu" <hjl@lucon.org> writes:

> S_IS_EXTERN just calls S_IS_EXTERNAL. Why does gas need it?

It doesn't.

In the non BFD_ASSEMBLER case, in obj-coff.h, S_IS_EXTERN and
S_IS_EXTERNAL are not identical.  Specifically, S_IS_EXTERNAL will
return true for a common symbol, and S_IS_EXTERN will not.  This is
almost certainly a bug.

Ian

  reply	other threads:[~2005-04-20  3:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 19:19 H. J. Lu
2005-04-20  3:07 ` Ian Lance Taylor [this message]
2005-04-20  4:27   ` H. J. Lu
2005-04-20  9:29     ` Nick Clifton
2005-04-20 14:32       ` PATCH: Remove S_IS_EXTERN H. J. Lu
2005-04-20 17:29         ` Nick Clifton

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=m33btmrvs7.fsf@gossamer.airs.com \
    --to=ian@airs.com \
    --cc=binutils@sources.redhat.com \
    --cc=hjl@lucon.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).