From: Gary Benson <gbenson@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Why GLIBC requires compiler optimizations to build
Date: Wed, 20 Jun 2018 10:35:00 -0000 [thread overview]
Message-ID: <CAHegJiJnmwqjBocN_caOxtn9-gBL3Aib6qS8vmE1bssUUDcubQ@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOoXbkKyOVCVL3zA7rm5jAOx+E1BL2G6wx1F2g-7ac1Tug@mail.gmail.com>
On 11 June 2018 at 22:48, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Mon, Jun 11, 2018 at 2:38 PM, Adhemerval Zanella <adhemerval.zanella@linaro.org> wrote:
> > It has been some time since I tried to build glibc without optimization
> > as an exercise and I can't really recall what exactly has prevented me
> > to accomplish it. So the question is if it is make sense to add such
> > requirement and if it is the case whether it would be a useful options
> > and what prevents us to do so?
>
> The main issue is to bootstrap ld.so to prevent dynamic relocations
> before it is ready.
Is it only really elf/rtld.c that specifically requires optimization then?
Thanks,
Gary
next prev parent reply other threads:[~2018-06-20 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 21:38 Adhemerval Zanella
2018-06-11 21:49 ` H.J. Lu
2018-06-20 10:35 ` Gary Benson [this message]
2018-06-20 12:51 ` Carlos O'Donell
2018-06-20 15:22 ` Gary Benson
2018-06-21 17:16 ` Carlos O'Donell
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=CAHegJiJnmwqjBocN_caOxtn9-gBL3Aib6qS8vmE1bssUUDcubQ@mail.gmail.com \
--to=gbenson@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--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).