From: Ian Lance Taylor <ian@zembu.com>
To: hjl@lucon.org
Cc: mark@codesourcery.com, binutils@sourceware.cygnus.com
Subject: Re: Your change to ldlang.c
Date: Fri, 02 Jul 1999 07:27:00 -0000 [thread overview]
Message-ID: <19990702142620.29296.qmail@daffy.airs.com> (raw)
In-Reply-To: <19990702065139.7A1CF57BA@ocean.lucon.org>
Date: Thu, 1 Jul 1999 23:51:39 -0700 (PDT)
From: hjl@lucon.org (H.J. Lu)
> Seems easy enough, but guess I'm missing something?
>
> Ian> Until quite recently (February 1999), .reginfo sections were
> Ian> not marked as LINK_ONCE, and they were instead handled in the
> Ian> emultempl file. The special handling was removed by this
> Ian> patch:
>
> I see. If I can't persuade you that my interpretation of
> SEC_LINK_ONCE is the One True Way :-), then may we revert this change?
>
I believe this change is needed for Linux/MIPS. Check with the
Linux/MIPS people before reverting it.
Actually, it was the Linux/MIPS people who suggested using LINK_ONCE
for .reginfo. Once that is done, the change to elf32.em becomes no
longer necessary (modulo concerns about ld -r). That is why they took
it out--not because they needed the change, but because other changes
they made meant that that code was no longer needed.
Ian
next prev parent reply other threads:[~1999-07-02 7:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 17:54 Mark Mitchell
1999-07-01 19:43 ` Ian Lance Taylor
1999-07-01 20:25 ` Mark Mitchell
1999-07-01 20:34 ` Ian Lance Taylor
1999-07-01 23:12 ` Mark Mitchell
1999-07-01 23:51 ` H.J. Lu
1999-07-02 7:27 ` Ian Lance Taylor [this message]
1999-07-02 16:31 ` Ralf Baechle
1999-07-02 1:00 ` Mikey
1999-07-02 7:25 ` Ian Lance Taylor
1999-07-02 7:40 ` Ian Lance Taylor
1999-07-02 10:30 ` Mark Mitchell
1999-07-06 18:35 ` Richard Henderson
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=19990702142620.29296.qmail@daffy.airs.com \
--to=ian@zembu.com \
--cc=binutils@sourceware.cygnus.com \
--cc=hjl@lucon.org \
--cc=mark@codesourcery.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).