From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: kill off the libgcc dependency
Date: Wed, 14 Jan 2015 11:48:27 +0000 [thread overview]
Message-ID: <20150114114827.GH4050@arm.com> (raw)
In-Reply-To: <3138622.1rQcFu1jAj@wuerfel>
On Wed, Jan 14, 2015 at 11:35:22AM +0000, Arnd Bergmann wrote:
> On Wednesday 14 January 2015 10:48:26 Will Deacon wrote:
> > On Wed, Jan 14, 2015 at 10:38:54AM +0000, Kevin Hao wrote:
> > > The arm64 doesn't depend on the libgcc to build the vmlinux image.
> >
> > Yes it does; we make use of __builtin_* for our bitops, for example.
> > The compiler guys don't guarantee that these will be inlined.
>
> Is that an architecture-specific statement?
I think the inlining guarantees apply to all architectures, but it affects
the arm64 kernel because we include <asm-generic/bitops/builtin-*>.
> The debate has been going on for ages in Linux, most architecture
> maintainers however decided against using libgcc and copy the functions
> that are actually needed into the kernel sources.
What's the benefit of copying them?
Will
next prev parent reply other threads:[~2015-01-14 11:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 10:38 [PATCH] arm64: kill off the libgcc dependency Kevin Hao
2015-01-14 10:48 ` Will Deacon
2015-01-14 11:35 ` Arnd Bergmann
2015-01-14 11:48 ` Will Deacon [this message]
2015-01-14 12:38 ` Arnd Bergmann
2015-01-14 12:52 ` Ard Biesheuvel
2015-01-14 13:37 ` Will Deacon
2015-01-15 7:07 ` Kevin Hao
2015-01-15 9:59 ` Will Deacon
2015-01-15 11:21 ` Ard Biesheuvel
2015-01-15 11:36 ` Will Deacon
2015-01-14 14:39 ` Russell King - ARM Linux
2015-01-15 7:09 ` Kevin Hao
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=20150114114827.GH4050@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).