This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: x86-64 related patch breaks cygwin bootstrap
- To: "Billinghurst, David (CRTS)" <David dot Billinghurst at riotinto dot com>, rth at cygnus dot com
- Subject: Re: x86-64 related patch breaks cygwin bootstrap
- From: Jan Hubicka <jh at suse dot cz>
- Date: Thu, 4 Oct 2001 14:04:34 +0200
- Cc: "'gcc-bugs at gcc dot gnu dot org'" <gcc-bugs at gcc dot gnu dot org>, "'bo at suse dot co dot uk'" <bo at suse dot co dot uk>, "'aj at suse dot de'" <aj at suse dot de>, "'jh at suse dot cz'" <jh at suse dot cz>
- References: <8D00C32549556B4E977F81DBC24E985D40FF93@crtsmail1.technol_exch.corp.riotinto.org>
> 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