[Bug bootstrap/42785] error: impossible constraint in 'asm'
--- Comment #2 from monaka at monami-software dot com 2010-01-18 23:29 --- (In reply to comment #1) If you use -arch ppc, then the host/build is really powerpc-apple-darwin so obviously you are configuring GCC incorrectly and the error message is correct as that is x86 inline-asm that is being compiled in that source. There is no need to use -arch option if we use powerpc-apple-darwin host/build. I think it can be resolved by a patch follows. diff --git a/gcc/config/i386/driver-i386.c b/gcc/config/i386/driver-i386.c index 17694ef..dc69a80 100644 --- a/gcc/config/i386/driver-i386.c +++ b/gcc/config/i386/driver-i386.c @@ -25,7 +25,7 @@ along with GCC; see the file COPYING3. If not see const char *host_detect_local_cpu (int argc, const char **argv); -#ifdef __GNUC__ +#if defined(__GNUC__) (defined(__i386__) || defined(__x86_64__)) #include cpuid.h struct cache_desc -- monaka at monami-software dot com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID | Summary|error: impossible constraint|error: impossible constraint |in �easm�f |in 'asm' http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42785
[Bug bootstrap/42785] error: impossible constraint in 'asm'
--- Comment #3 from pinskia at gcc dot gnu dot org 2010-01-19 00:10 --- driver-i386.c should not be included if you are compiling for a PPC host/build really. So it is a problem of you misconfiguring GCC really and nothing else. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||INVALID http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42785
[Bug bootstrap/42785] error: impossible constraint in 'asm'
--- Comment #4 from pinskia at gcc dot gnu dot org 2010-01-19 00:13 --- More to the point, use lipo to combine the gcc drivers after the fact to get a dual arch executable. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42785
[Bug bootstrap/42785] error: impossible constraint in 'asm'
--- Comment #5 from monaka at monami-software dot com 2010-01-19 02:42 --- (In reply to comment #3) driver-i386.c should not be included if you are compiling for a PPC host/build really. So it is a problem of you misconfiguring GCC really and nothing else. I see what you want to say, but. The another viewpoint: In i386-driver.c, there is decided by #ifdef __GNUC__ which host_detect_local_cpu (dummy or not) is used In i386.h, there is decided by #if defined(__i386__) || defined(__x86_64__) if it defines EXTRA_SPEC_FUNCTIONS . They are inconsistent, right? P.S. Thanks for your information about lipo. I know about it and I've already released binary distributions. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42785
[Bug bootstrap/42785] error: impossible constraint in 'asm'
--- Comment #6 from pinskia at gcc dot gnu dot org 2010-01-19 02:45 --- They are inconsistent, right? No because i386-driver.c is only supposed to be compiled with a x86 or x86_64 compiler. Really the file could have #if !defined(__i386__) !defined(__x86_64__) #error This should only be compiled with an x86 compiler #endif And still be correct. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42785