------- Comment #3 from jan dot kratochvil at redhat dot com 2008-10-07 23:10 ------- FYI I find at least this specific reported testcase as already fixed by Jason:
http://gcc.gnu.org/ml/gcc-patches/2008-09/msg00729.html http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00189.html GCC now even produces different mangled names: GNU C++ (GCC) version 4.4.0 20081007 (experimental) (x86_64-unknown-linux-gnu) compiled by GNU C version 4.4.0 20081007 (experimental), GMP version 4.2.2, MPFR version 2.3.1. 00000000004005c3 w F .text 000000000000003f _Z1fIdIiEEiT_DpT0_ 0000000000400602 w F .text 0000000000000012 _Z1fIiIEEiT_DpT0_ 0000000000400584 w F .text 000000000000003f _Z1fIiIdiEEiT_DpT0_ 00000000004005c3 w F .text 000000000000003f int f<double, int>(double, int) 0000000000400602 w F .text 0000000000000012 int f<int, >(int, ) 0000000000400584 w F .text 000000000000003f int f<int, double, int>(int, double, int) -- jan dot kratochvil at redhat dot com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jan dot kratochvil at redhat | |dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37718
