[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#182795: gcc-3.2: mpqc build fails on MIPS with 'Branch out of range' error



On Fri, Feb 28, 2003 at 12:00:35AM +0100, Michael Banck wrote:
> Package: gcc-3.2
> Version: 1:3.2.3-0pre2
> Severity: normal
> 
> Hi,
> 
> compiling mpqc on MIPS results in this error:
> 
>  /usr/bin/gcc-3.2 -DHAVE_CONFIG_H -D_REENTRANT  -I../../../../../src/lib
> -I/build/buildd/mpqc-2.1.3/include -I/build/buildd/mpqc-2.1.3/src/lib  -O0
> -Wall -c /build/buildd/mpqc-2.1.3/src/lib/chemistry/qc/dft/lebedev.c
> -o lebedev.o
>  /tmp/ccIsYgSV.s: Assembler messages:
>  /tmp/ccIsYgSV.s:361: Error: Branch out of range
>  /tmp/ccIsYgSV.s:366: Error: Branch out of range
> [...]
>  /tmp/ccIsYgSV.s:19541: Error: Branch out of range
>  /tmp/ccIsYgSV.s:22425: Error: Branch out of range
>  make[6]: *** [lebedev.o] Error 1
>  make[6]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry/qc/dft'
>  make[5]: *** [default] Error 1
>  make[5]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry/qc'
>  make[4]: *** [default] Error 1
>  make[4]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib/chemistry'
>  make[3]: *** [default] Error 1
>  make[3]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src/lib'
>  make[2]: *** [default] Error 1
>  make[2]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static/src'
>  make[1]: *** [default] Error 1
>  make[1]: Leaving directory `/build/buildd/mpqc-2.1.3/build-static'
>  make: *** [build-static-stamp] Error 2
> 
> see http://buildd.debian.org/fetch.php?&pkg=mpqc&ver=2.1.3-2&arch=mipsel&; \ 
> 	stamp=1046045555&file=log&as=raw for the full buildd log.
> 
> This error also occured on gcc-2.95, I did not file it earlier because I
> was hoping that it might be gone in gcc-3.2. The first builds in early
> 2002 were done with -O and then with -O0 afterwards.
> 
> You can get the source file at
> 
> http://people.debian.org/~mbanck/lebedev.c

FYI, there should be a new binutils which avoids this issue "soon". 
It's a compiler bug, though - someone should try using gcc-snapshot. 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer



Reply to: