From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Allan McRae <allan@archlinux.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Don't use PLT nor GOT in libc.a [BZ #20750]
Date: Mon, 28 Nov 2016 18:27:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1611281825510.19633@digraph.polyomino.org.uk> (raw)
In-Reply-To: <CAMe9rOpcyETFMbJrDu2PontwYnyKX9Q+4jUj-BrATDFp_p7K8A@mail.gmail.com>
Does this fix bug 20621 or not? (At one point 20621 and 20750 were marked
as duplicates.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2016-11-28 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 17:47 H.J. Lu
2016-11-04 19:03 ` Florian Weimer
2016-11-04 19:25 ` H.J. Lu
2016-11-07 16:03 ` Florian Weimer
2016-11-07 17:14 ` H.J. Lu
2016-11-24 11:58 ` Allan McRae
2016-11-25 8:43 ` Florian Weimer
2016-11-28 17:46 ` H.J. Lu
2016-11-28 18:27 ` Joseph Myers [this message]
2016-11-28 21:32 ` H.J. Lu
2016-11-28 17:54 ` Szabolcs Nagy
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=alpine.DEB.2.20.1611281825510.19633@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=allan@archlinux.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.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).