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

Bug#175478: g77-3.2: Internal error encountered compiling octave 2.1

Package: g77-3.2
Version: +N/A; reported 2003-01-05
Severity: important

This applies to g77-3.2 on m68k as detailed below in an email I first sent
to the m68k build crew, and John Eaton, Octave's author.

Let me know if you need more help. John does provide some more detail below,
and the buildd logs have more as well.


On Sun, Jan 05, 2003 at 02:49:39PM -0600, John W. Eaton wrote:
> On  5-Jan-2003, Dirk Eddelbuettel <edd@debian.org> wrote:
> | 
> | >From the build log, and note that I already switch debugging and optimisation
> | off on m68k:
> | 
> | /usr/bin/g77-3.2 -c -fPIC -O0 -g0 zbknu.f -o pic/zbknu.o
> | zbknu.f: In subroutine `zbknu':
> | zbknu.f:567: Internal compiler error in instantiate_virtual_regs_1, at function.c:3980
> | Please submit a full bug report,
> | with preprocessed source if appropriate.
> | See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
> | 
> | Please see full details at 
> | 
> | http://buildd.debian.org/fetch.php?&pkg=octave2.1&ver=2.1.43-2&arch=m68k&stamp=1041790412&file=log&as=raw
> | 
> | Let me know if you want me to report this as a g77-3.2 bug.  Octave 2.1 now
> | requires gcc 3.2.
> I'd say yes, you should report it as a bug unless we can verify that
> it doesn't happen with the latest g77/gcc sources.
> I don't see anything particularly special about amos/zbknu.f, but it
> is a relatively large subroutine with a lot of local variables.  So
> given that and the error message above, it looks like we've triggered
> a register allocation bug.  The file function.c is part of the gcc
> backend, I think.  It is in the gcc subdirectory of the gcc sources,
> not the fortran front end directory.
> jwe

Prediction is very difficult, especially about the future. 
				             -- Niels Bohr

Reply to: