From: Jens Axboe <axboe@kernel.dk>
To: Aaron Carroll <xaaronc@gmail.com>
Cc: "Krishnamurthy, Anush" <anush.krishnamurthy@intel.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Make FIO for Android
Date: Fri, 12 Apr 2013 09:00:34 +0200 [thread overview]
Message-ID: <20130412070034.GI12244@kernel.dk> (raw)
In-Reply-To: <CAKCZDgkXzGvvdUaYqqR0-3zV==spgU=8QA757CfnRwFbdVj_JA@mail.gmail.com>
On Fri, Apr 12 2013, Aaron Carroll wrote:
> tuff
> > should be basic enough that it isn't a lot of trouble to carry it. At
> > least when we figure out why the Android NDK doesn't like the current
> > restraints :-)
>
> Digging around the GCC headers seems to have helped. If you change
> the constraint on ebx to:
> : "=a" (*eax), "=r" (*ebx), "=c" (*ecx), "=d" (*edx)
> then it builds.
But it doesn't work, we lose the output :-)
> The relevant comment from cpuid.h:
> /* %ebx may be the PIC register. */
> which is ifdef'd on __PIC__
>
> Dunno what that means, but it builds with that, plus a very small
> Android-specific fix. Both in attached patch.
Patch is garbled?
--
Jens Axboe
next prev parent reply other threads:[~2013-04-12 7:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-11 17:57 Make FIO for Android Krishnamurthy, Anush
[not found] ` <CAKCZDgnM85AcwD6Ss5YWNjXwY-OE7QFQh22nFdEFHkta_N0hRA@mail.gmail.com>
2013-04-12 1:20 ` Krishnamurthy, Anush
2013-04-12 2:48 ` Aaron Carroll
2013-04-12 3:17 ` Krishnamurthy, Anush
2013-04-12 3:28 ` Aaron Carroll
2013-04-12 3:37 ` Aaron Carroll
2013-04-12 5:58 ` Jens Axboe
2013-04-12 6:10 ` Aaron Carroll
2013-04-12 6:18 ` Jens Axboe
2013-04-12 6:24 ` Aaron Carroll
2013-04-12 6:30 ` Jens Axboe
2013-04-12 6:34 ` Aaron Carroll
2013-04-12 6:38 ` Jens Axboe
2013-04-12 6:51 ` Aaron Carroll
2013-04-12 7:00 ` Jens Axboe [this message]
2013-04-12 7:10 ` Aaron Carroll
2013-04-12 7:12 ` Aaron Carroll
2013-04-12 7:16 ` Jens Axboe
2013-04-12 7:22 ` Aaron Carroll
2013-04-12 8:04 ` Jens Axboe
2013-04-13 3:47 ` Aaron Carroll
2013-04-13 18:05 ` Jens Axboe
2013-04-14 5:28 ` Aaron Carroll
2013-04-14 8:13 ` Jens Axboe
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=20130412070034.GI12244@kernel.dk \
--to=axboe@kernel.dk \
--cc=anush.krishnamurthy@intel.com \
--cc=fio@vger.kernel.org \
--cc=xaaronc@gmail.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