This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: 2nd Stage of xGCC -- failure

To: Lukas Ruf <ruf at tik dot ee dot ethz dot ch>
Subject: Re: 2nd Stage of xGCC -- failure
From: Philip Blundell <philb at gnu dot org>
Date: Thu, 12 Apr 2001 10:25:19 +0100
cc: Yves Rutschle <y dot rutschle at indigovision dot com>, Cross GCC <crossgcc at sourceware dot cygnus dot com>
References: <c=US%a=_%p=Indigo_Active_Vi%l=CRIANLARICH-010412084626Z-8704@crianlarich.indigo-avs.com> <20010412110803.E13507@tik.ee.ethz.ch>

>#define __llrint_code \
>  long long int __llrintres;                  \
>  __asm__ __volatile__                    \
>    ("fistpll %0"                   \
>     : "=m" (__llrintres) : "t" (__x) : "st");              \
>  return __llrintres
>__MATH_INLINE long long int

This is totally not ARM code.  You need to find out where the macro is coming 
from and stop that from happening.

p.



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

Follow-Ups:
- Re: 2nd Stage of xGCC -- failure
  - From: Lukas Ruf

References:
- RE: 2nd Stage of xGCC -- failure
  - From: Yves Rutschle
- Re: 2nd Stage of xGCC -- failure
  - From: Lukas Ruf

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]