Your message dated Sat, 18 Jun 2016 00:52:54 +0200
with message-id <[email protected]>
and subject line closing bugs reported against ancient GCC versions
has caused the Debian Bug report #466791,
regarding [PR target/35079] gfortran-4.3: ICE on arm with -O1 -funroll-loops
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
466791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466791
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gfortran-4.3
Version: 4.3-20080202-1
Severity: normal
Hi gcc maintainers,
In transitioning CERNLIB to gfortran, I've uncovered an ICE [1] that
occurs on arm when gfortran-4.3 is called with -funroll-loops and -O1 or
higher. (If -funroll-loops is not given, gfortran succeeds on arm even
at -O3.)
I put together a self-contained test case from the CERNLIB source files
at [2] for your convenience. The tarball there already includes the
intermediate .f and .s files generated by the failing command on an arm
machine (agnesi.debian.org).
[1]
http://buildd.debian.org/fetch.cgi?&pkg=cernlib&ver=2006.dfsg.2-9&arch=arm&stamp=1203539055
[2] http://people.debian.org/~kmccarty/arm-ICE-test.tar.gz
best regards,
--
Kevin B. McCarty <[email protected]>
WWW: http://www.starplot.org/
WWW: http://people.debian.org/~kmccarty/
GPG: public key ID 4F83C751
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
This bug has been reported against an ancient version of
gpc (4.1), gcc/g++/gfortran (4.3), or gcj/gij/gobjc (4.4), that was last
released with Debian 6.0 (squeeze). But even squeeze-lts has now reached
end-of-life and is no longer supported.
The bug is assumed to be fixed (or no longer relevant) in newer GCC
releases and therefore I'm closing this report now. If the problem is
still reproducible in the currently supported versions (gcc-5, gcc-6 or
corresponding g++/gcj), feel free to provide more information, reopen
and reassign this bug report.
Andreas
--- End Message ---
