From: Alan Modra <amodra@bigpond.net.au>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com, aaron98wiridge9@aaronwl.com,
gcc@gcc.gnu.org
Subject: Re: PATCH: PR 528: .set is broken for weak symbols
Date: Tue, 09 Nov 2004 00:58:00 -0000 [thread overview]
Message-ID: <20041109005805.GC12837@bubble.modra.org> (raw)
In-Reply-To: <20041109003025.GA19446@lucon.org>
On Mon, Nov 08, 2004 at 04:30:25PM -0800, H. J. Lu wrote:
> PR 528
> * symbols.c (resolve_symbol_value): Convert weak symbols only
> for Windows PECOFF.
> (symbol_equated_reloc_p): Don't equate weaks when relocating
> only for Windows PECOFF.
Please commit if you haven't done so already, and close pr 528.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2004-11-09 0:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 0:15 .set is broken H. J. Lu
2004-11-09 0:30 ` PATCH: PR 528: .set is broken for weak symbols H. J. Lu
2004-11-09 0:58 ` Alan Modra [this message]
2004-11-09 6:47 ` Aaron W. LaFramboise
2004-11-09 16:29 ` H. J. Lu
2004-11-09 21:29 ` Aaron W. LaFramboise
2004-11-10 0:17 ` H. J. Lu
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=20041109005805.GC12837@bubble.modra.org \
--to=amodra@bigpond.net.au \
--cc=aaron98wiridge9@aaronwl.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--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).