Flexible I/O Tester development
 help / color / mirror / Atom feed
* Build error in Android/x86
@ 2013-03-15  6:45 Aaron Carroll
  2013-03-15 16:10 ` Jens Axboe
  0 siblings, 1 reply; 2+ messages in thread
From: Aaron Carroll @ 2013-03-15  6:45 UTC (permalink / raw)
  To: fio

I'm trying to build FIO with an Android/x86 cross compiler:

  make CROSS_COMPILE=~/dev/android-toolchains-r8c/x86-4.6/bin/i686-linux-android-

but get the following error:

   arch/arch-x86-common.h:9:2: error: inconsistent operand constraints in an 'asm'

which is complaining about this function:

   static inline void do_cpuid(unsigned int *eax, unsigned int *ebx,
                   unsigned int *ecx, unsigned int *edx)
   {
       asm volatile("cpuid"
           : "=a" (*eax), "=b" (*ebx), "=c" (*ecx), "=d" (*edx)
           : "0" (*eax), "2" (*ecx)
           : "memory");
   }

Unfortunately I don't do x86 ASM.  I'm wondering if this is a genuine error, or 
if something has broken in the cross compile.



Cheers,
     -- Aaron


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Build error in Android/x86
  2013-03-15  6:45 Build error in Android/x86 Aaron Carroll
@ 2013-03-15 16:10 ` Jens Axboe
  0 siblings, 0 replies; 2+ messages in thread
From: Jens Axboe @ 2013-03-15 16:10 UTC (permalink / raw)
  To: Aaron Carroll; +Cc: fio

On Fri, Mar 15 2013, Aaron Carroll wrote:
> I'm trying to build FIO with an Android/x86 cross compiler:
> 
>  make CROSS_COMPILE=~/dev/android-toolchains-r8c/x86-4.6/bin/i686-linux-android-
> 
> but get the following error:
> 
>   arch/arch-x86-common.h:9:2: error: inconsistent operand constraints in an 'asm'
> 
> which is complaining about this function:
> 
>   static inline void do_cpuid(unsigned int *eax, unsigned int *ebx,
>                   unsigned int *ecx, unsigned int *edx)
>   {
>       asm volatile("cpuid"
>           : "=a" (*eax), "=b" (*ebx), "=c" (*ecx), "=d" (*edx)
>           : "0" (*eax), "2" (*ecx)
>           : "memory");
>   }
> 
> Unfortunately I don't do x86 ASM.  I'm wondering if this is a genuine error,
> or if something has broken in the cross compile.

Hmm, I wonder why it complains about that, looks legit to me... Maybe
it's the ecx being both input and output it doesn't like?

-- 
Jens Axboe


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-03-15 16:11 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-03-15  6:45 Build error in Android/x86 Aaron Carroll
2013-03-15 16:10 ` Jens Axboe

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox