2.95.2/Linux internal compiler error on assert(!template_fn<...>(...))
Jonathan Thornburg
jthorn@galileo.thp.univie.ac.at
Fri Jan 14 12:05:00 GMT 2000
In message <199911211542.QAA29833@mach.thp.univie.ac.at>
(dated 21 Nov 1999), available on the gcc-bugs mailing list archives at
http://gcc.gnu.org/ml/gcc-bugs/1999-11/msg00654.html
I reported that
| On a Red Hat GNU/Linux 6.0 i586 system, gcc 2.95.2 gives an internal
| compiler error on the C++ source code line
|
| assert(! fuzzy<fp>::EQ(fabs( mu_bar), 0.5*PI));
|
| where bool fuzzy<fp>::EQ(fp, fp) is a template function, fp is
| a typedef for double , and PI is #defined to 3.14159... :
|
| % /space/try/bin/g++ -Wall -fsyntax-only -I/home/jthorn coords.cc
| coords.cc:277: Internal compiler error.
| coords.cc:277: Please submit a full bug report.
| coords.cc:277: See <URL: http://www.gnu.org/software/gcc/faq.html#bugreport > for instructions.
| %
|
| Interestingly, on a SunOS 4.1.3 sparc v7 system, gcc 2.95.2 does *not*
| give an internal compiler error on this same code (that is, *my* code
| is the same; the system header files are of course now gcc's fixed versions
| of the SunOS ones instead of the GNU/Linux ones). This might due to a
| platform-dependent #ifdef in my code, but I suspect it's more likely due
| to a different assert() macro.
Did this bug report somehow fall into a black hole? I recieved
no followup correspondence about it, and the gcc-bugs mailing list
archive shows no followups. Would resubmission be desirable?
Thanks 1L<<20,
--
-- Jonathan Thornburg <jthorn@galileo.thp.univie.ac.at>
http://www.thp.univie.ac.at/~jthorn/home.html
Universitaet Wien (Vienna, Austria) / Institut fuer Theoretische Physik
"If the code and the comments disagree, then both are probably wrong."
-- Norm Schryer
More information about the Gcc-bugs
mailing list