From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Barry Song <bs14@csr.com>, Barry Song <21cnbao@gmail.com>,
Zhiwu Song <zhiwu.song@csr.com>,
Binghua Duan <binghua.duan@csr.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: prevent compilers from optimising pll calculation into __aeabi__uldivmod
Date: Wed, 27 Apr 2011 16:06:08 +0100 [thread overview]
Message-ID: <20110427150607.GD31952@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF0497F1AA8C@HQMAIL01.nvidia.com>
On Wed, Apr 27, 2011 at 07:59:39AM -0700, Stephen Warren wrote:
> Aren't there compiler flags that tell gcc it isn't operating in a hosted(?)
> environment, and hence not to emit calls to these functions? If so, I
> imagine they should be added to the kernel's core (or ARM arch ) makefiles.
IIRC there's some intrinsics (usually for operations like divisions)
which GCC expects to be provided even in a free standing environment.
next prev parent reply other threads:[~2011-04-27 15:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 14:59 [PATCH] ASoC: prevent compilers from optimising pll calculation into __aeabi__uldivmod Stephen Warren
2011-04-27 15:06 ` Mark Brown [this message]
2011-04-27 15:09 ` Barry Song
2011-04-27 15:45 ` Barry Song
2011-04-27 17:10 ` [alsa-devel] " Nicolas Pitre
-- strict thread matches above, loose matches on Subject: below --
2011-04-27 7:27 Barry Song
2011-04-27 8:19 ` Takashi Iwai
2011-04-27 8:24 ` Barry Song
2011-04-27 8:41 ` Takashi Iwai
2011-04-27 8:50 ` Barry Song
2011-04-27 14:30 ` Mark Brown
2011-04-27 15:00 ` [alsa-devel] " Barry Song
2011-04-27 15:12 ` Mark Brown
2011-04-27 22:30 ` [alsa-devel] " Michael Hope
2011-04-28 11:40 ` Mark Brown
2011-04-27 8:49 ` Mark Brown
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=20110427150607.GD31952@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=21cnbao@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=binghua.duan@csr.com \
--cc=bs14@csr.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lrg@slimlogic.co.uk \
--cc=swarren@nvidia.com \
--cc=zhiwu.song@csr.com \
/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