x86-64 related patch breaks cygwin bootstrap

Jan Hubicka jh@suse.cz
Thu Oct 4 05:04:00 GMT 2001


> The following patch breaks cygwin bootstrap.  Let me know if/how I can help
> resolve this.
> /usr/local/src/gcc-junk/gcc/varasm.c: In function `assemble_integer':
> /usr/local/src/gcc-junk/gcc/varasm.c:1936: `ASM_QUAD' undeclared (first use
> in t
> his function)
> /usr/local/src/gcc-junk/gcc/varasm.c:1936: (Each undeclared identifier is
> report
> ed only once

Uhm, I see.
This is weird, why cygwin don't use att.h for assembler definitions, as Linux port
does?

I am not quite sure if it is cleaner to ifdef around each ASM_QUAD use, or if we can
just define ASM_QUAD to ".quad" everywhere...

Richard?
Honza
> /usr/local/src/gcc-junk/gcc/varasm.c:1936: for each function it appears in.)
> /usr/local/src/gcc-junk/gcc/varasm.c: At top level:
> /usr/local/src/gcc-junk/gcc/varasm.c:5008: warning:
> `remove_from_pending_weak_li
> st' defined but not used
> make[2]: *** [varasm.o] Error 1
> make[2]: Leaving directory `/usr/local/obj/gcc-j/gcc'
> make[1]: *** [stage1_build] Error 2
> make[1]: Leaving directory `/usr/local/obj/gcc-j/gcc'
> make: *** [bootstrap] Error 2



More information about the Gcc-bugs mailing list