Bug#975219: [Debichem-devel] Bug#975219: elkcode: FTBFS: internal compiler error: in lookup_field_for_decl, at tree-nested.c:288
Hi Lucas, That looks like an ICE, shouldn't that be filed with gfortran? On Thu, Nov 19, 2020 at 10:52:05AM +0100, Lucas Nussbaum wrote: > > mpif90 `dpkg-buildflags --get FFLAGS` `dpkg-buildflags --get CPPFLAGS` > > -Wall -ffast-math -funroll-loops -fopenmp -fallow-argument-mismatch > > `dpkg-buildflags --get LDFLAGS` -c exxengy.f90 > > exxengy.f90:6:18: > > > > 6 | subroutine exxengy > > | ^ > > internal compiler error: in lookup_field_for_decl, at tree-nested.c:288 > > 0x71106d lookup_field_for_decl > > ../../src/gcc/tree-nested.c:288 > > 0x111523e convert_local_reference_stmt > > ../../src/gcc/tree-nested.c:2408 [...] > > Please submit a full bug report, > > with preprocessed source if appropriate. > > Please include the complete backtrace with any bug report. > > See for instructions. > > make[3]: *** [Makefile:194: exxengy.o] Error 1 Michael
Bug#975219: [Debichem-devel] Bug#975219: elkcode: FTBFS: internal compiler error: in lookup_field_for_decl, at tree-nested.c:288
Hi Michael, On 22/11/20 at 15:32 +0100, Michael Banck wrote: > Hi Lucas, > > That looks like an ICE, shouldn't that be filed with gfortran? Usually my logic is: if there's only one similar failure, I file a bug against the affected package, rather than against the toolchain package or the library, because it might be something very strange with the package that is causing the toolchain to misbehave. (In that case, that was the only ICE; and I also notified doko about it on IRC) Lucas
Bug#975219: [Debichem-devel] Bug#975219: elkcode: FTBFS: internal compiler error: in lookup_field_for_decl, at tree-nested.c:288
* Lucas Nussbaum: > Hi Michael, > > On 22/11/20 at 15:32 +0100, Michael Banck wrote: >> Hi Lucas, >> >> That looks like an ICE, shouldn't that be filed with gfortran? > > Usually my logic is: if there's only one similar failure, I file a bug > against the affected package, rather than against the toolchain package > or the library, because it might be something very strange with the > package that is causing the toolchain to misbehave. ICEs are still consider GCC bugs (by upstream, maybe not by Debian), as long as they are reproducible and not the result of faulty hardware.
