This is the mail archive of the
ecos-discuss@sourceware.cygnus.com
mailing list for the eCos project.
Re: SH Tool Building Problem (egcs-20000403 snapshot)
- To: "John M. Mills" <jmills at tga dot com>
- Subject: Re: [ECOS] SH Tool Building Problem (egcs-20000403 snapshot)
- From: Jonathan Larmour <jlarmour at redhat dot co dot uk>
- Date: Thu, 06 Apr 2000 21:54:38 +0100
- CC: eCos Discussion <ecos-discuss at sourceware dot cygnus dot com>
- Organization: Red Hat UK Ltd.
- References: <Pine.WNT.4.10.10004061413320.121-100000@Jmills.tga>
"John M. Mills" wrote:
>
> I trying to build the eCos toolset for Hitachi SH processors under
> WinNT/SP4, and failing with egcs-20000403.
>
> I did fresh installations of Cygwin-B20.1 and gcc-2_95_2-cygb20.tar.gz.
>
> I built and installed binutils-000404 and added their (exec-prefix)/bin to
> my path.
It's definitely not a problem with cygwin, binutils or your native gcc.
> _fixunssfsi
> /c/usr/src/egcs-20000403/gcc/libgcc2.c: In function `__fixunssfsi':
> /c/usr/src/egcs-20000403/gcc/libgcc2.c:1026: Insn does not satisfy its constraints:
> (insn 59 55 4 (set (reg:SI 0 r0)
> (reg:SI 28 fr4)) 123 {movsi_ie} (nil)
> (nil))
> /c/usr/src/egcs-20000403/gcc/libgcc2.c:1026: Internal compiler error in `reload_cse_simplify_operands', at reload1.c:8130
> Please submit a full bug report.
> See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
> make[3]: *** [libgcc2.a] Error 1
> make[3]: Leaving directory `/c/build/egcs/gcc'
> make[2]: *** [stmp-multilib-sub] Error 2
> make[2]: Leaving directory `/c/build/egcs/gcc'
> make[1]: *** [stmp-multilib] Error 1
> make[1]: Leaving directory `/c/build/egcs/gcc'
> make: *** [all-gcc] Error 2
> make: Leaving directory `/c/build/egcs'
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
>
> I got similar results with other snapshots. Does this look familiar to
> anyone?
I've seen this class of error before and it is "simply" a compiler error in
the snapshot. You should probably do what it says and report it as a bug,
or go to http://gcc.gnu.org/ and join the gcc@gcc.gnu.org mailing list and
ask there, but you'd probably be told to report it as a bug in the proper
way :-).
You could set TARGET_LIBGCC2_FLAGS=-O1 in gcc/config/sh/t-sh, which might
help (although it will result in slower code in libgcc obviously).
Alternatively, try a slightly older snapshot. I know that the egcs-20000313
snapshot worked for me for sh-elf.
I'm sure the GCC team would appreciate it if you could report it as per
http://www.gnu.org/software/gcc/bugs.html anyway.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault