From: Steve Ellcey <sellcey@mips.com>
To: "Maciej W. Rozycki" <macro@codesourcery.com>
Cc: Richard Henderson <rth@twiddle.net>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"libc-ports@sourceware.org" <libc-ports@sourceware.org>,
Chung-Lin Tang <cltang@codesourcery.com>,
<rdsandiford@googlemail.com>
Subject: Re: [PATCH 2/2] MIPS16: MIPS16 support proper
Date: Mon, 28 Jan 2013 21:17:00 -0000 [thread overview]
Message-ID: <1359407838.32571.23.camel@ubuntu-sellcey> (raw)
In-Reply-To: <alpine.DEB.1.10.1301282042020.4409@tp.orcam.me.uk>
On Mon, 2013-01-28 at 21:06 +0000, Maciej W. Rozycki wrote:
> On Mon, 28 Jan 2013, Richard Henderson wrote:
>
> > And of course as you note elsewhere, this is an excellent time to
> > have new toolchains stop using .init, as DT_INIT_ARRAY has none of
> > these problems.
>
> Given the above I think we need it sooner rather than later. Who's got
> the power to make it happen?
>
> Maciej
Would switching from .init to DT_INIT_ARRAY be an incompatible ABI
change? I think I remember the GNU linker can handle mixing both types
of sections in one executable but I am not sure if that is right.
I added Richard Sandiford to this email in case he hasn't seen it on the
libc mailing lists.
Steve Ellcey
sellcey@mips.com
next prev parent reply other threads:[~2013-01-28 21:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 4:41 [PATCH 0/2] MIPS16: MIPS16 support Maciej W. Rozycki
2013-01-23 4:41 ` [PATCH 1/2] MIPS16: Allocate GLIBC_2.18 Maciej W. Rozycki
2013-01-23 4:42 ` [PATCH 2/2] MIPS16: MIPS16 support proper Maciej W. Rozycki
2013-01-23 17:22 ` Joseph S. Myers
2013-01-24 10:10 ` Chung-Lin Tang
2013-01-24 13:13 ` Maciej W. Rozycki
2013-01-24 13:56 ` Richard Sandiford
2013-02-20 16:19 ` [PATCH v2] MIPS: MIPS16 support Maciej W. Rozycki
2013-02-20 16:29 ` Joseph S. Myers
2013-02-27 1:38 ` [PATCH v3] " Maciej W. Rozycki
2013-02-27 17:50 ` Joseph S. Myers
2013-02-27 23:54 ` Maciej W. Rozycki
2013-01-24 18:08 ` [PATCH 2/2] MIPS16: MIPS16 support proper Ellcey, Steve
2013-01-25 5:14 ` Maciej W. Rozycki
2013-01-25 13:59 ` Richard Sandiford
2013-01-28 22:18 ` Steve Ellcey
2013-01-25 22:10 ` Steve Ellcey
2013-01-26 0:32 ` Maciej W. Rozycki
2013-01-28 17:36 ` Steve Ellcey
2013-01-28 17:56 ` Steve Ellcey
2013-01-28 21:08 ` Maciej W. Rozycki
2013-01-28 18:58 ` Richard Henderson
2013-01-28 21:06 ` Maciej W. Rozycki
2013-01-28 21:17 ` Steve Ellcey [this message]
2013-01-29 16:24 ` Richard Henderson
2013-01-29 19:27 ` Joseph S. Myers
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=1359407838.32571.23.camel@ubuntu-sellcey \
--to=sellcey@mips.com \
--cc=cltang@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=macro@codesourcery.com \
--cc=rdsandiford@googlemail.com \
--cc=rth@twiddle.net \
/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).