From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gcc: Support configure option --with-linker-hash-style
Date: Sun, 17 Dec 2017 16:30:59 +0200 [thread overview]
Message-ID: <05e7f492-8a32-5f93-701d-377442ccd2b9@petroprogram.com> (raw)
In-Reply-To: <20171216162337.667a30da@windsurf>
Hi Thomas
Well, I was just worried that if setting the linking hash style to stone
(aka "gnu") then could
it maybe break builds in some other archs than x86, x86_64 and ARM ?
So I played carefull and made it configurable by choice.
Im not sure but I think that option has been hiding in GCC since 4.x and
buildroot lowest is 4.9.
So if it's okay I can cook another patch where it just set's it in stone
without choice ?
-S-
Thomas Petazzoni kirjoitti 16.12.2017 klo 17:23:
> Hello,
>
> On Sat, 16 Dec 2017 01:25:30 +0200, Stefan Fr?berg wrote:
>> This will set the default hash style that GCC will
>> always use during linking.
>>
>> Signed-off-by: Stefan Fr?berg <stefan.froberg@petroprogram.com>
> Could you explain the motivation for configuring the default hash
> style? If "gnu" gives the best application startup time, why would we
> use a different one?
>
> Generally, the commit log lacks a bit of background, i.e the "why" we
> would want such a change.
>
> Thanks!
>
> Thomas
next prev parent reply other threads:[~2017-12-17 14:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 23:25 [Buildroot] [PATCH 1/1] gcc: Support configure option --with-linker-hash-style Stefan Fröberg
2017-12-15 23:27 ` [Buildroot] FW: " Kees van Unen
2017-12-16 1:50 ` Carlos Santos
2017-12-16 1:51 ` [Buildroot] FW: " Kees van Unen
2017-12-16 12:11 ` [Buildroot] " Thomas Petazzoni
2017-12-16 15:23 ` [Buildroot] " Thomas Petazzoni
2017-12-17 14:30 ` Stefan Fröberg [this message]
2018-11-08 23:49 ` Romain Naour
2018-11-09 21:35 ` Arnout Vandecappelle
2018-11-10 11:30 ` Romain Naour
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=05e7f492-8a32-5f93-701d-377442ccd2b9@petroprogram.com \
--to=stefan.froberg@petroprogram.com \
--cc=buildroot@busybox.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