From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: kill off the libgcc dependency
Date: Thu, 15 Jan 2015 09:59:19 +0000 [thread overview]
Message-ID: <20150115095918.GA23475@arm.com> (raw)
In-Reply-To: <20150115070730.GA23621@pek-khao-d1.corp.ad.wrs.com>
On Thu, Jan 15, 2015 at 07:07:30AM +0000, Kevin Hao wrote:
> On Wed, Jan 14, 2015 at 01:37:42PM +0000, Will Deacon wrote:
> > On Wed, Jan 14, 2015 at 12:52:49PM +0000, Ard Biesheuvel wrote:
> > > IMO libgcc.a cannot be used at all in the kernel, as it is not built
> > > with -mgeneral-regs-only so we have no guarantee that it will leave
> > > the NEON registers alone.
> >
> > That's a very good point. In which case, we'd need to extend this patch
> > to implement the bitops that we currently rely on the __builtins for.
>
> Sorry, I am not sure I get what you mean. These builtin functions for bitops
> are not implemented in the libgcc, they are inlined in compiler. So why do
> we need to reimplement these bitops when removing the link with libgcc?
I'm just relaying what the tools guys told us. Namely, that they don't
guarantee that they are inlined and could generate a branch to a libgcc
function. As Ard says, they could also use fpsimd registers, so whether
or not they are inlined is moot anyway.
Will
next prev parent reply other threads:[~2015-01-15 9:59 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
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 [this message]
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=20150115095918.GA23475@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).