Mark Mitchell wrote:
> No, that's very weird; that was PR 23993, which I fixed. Or, thought I
> did. It's definitely fixed for me on x86_64-unknown-linux-gnu. But,
> the nature of the bug didn't seem at all system-dependent. I've checked
> that I have no local patches in my GCC 4.0.x tree. So, I'm pretty
> mystified...
Well, current 4_0 branch fixes the problem for me too. It appears that
the test case made it into the release, but the fix didn't ...
Comparing the cp/ChangeLog files from 4.0.2 and the 4_0 branch, it looks
like the fix is in the release according to the current ChangeLog, but
in fact it wasn't:
[EMAIL PROTECTED] fsf]$ diff -u gcc-4.0.2/gcc/cp/ChangeLog
gcc-4_0/gcc/cp/ChangeLog
--- gcc-4.0.2/gcc/cp/ChangeLog 2005-09-21 05:56:51.000000000 +0200
+++ gcc-4_0/gcc/cp/ChangeLog 2005-09-30 12:40:52.000000000 +0200
@@ -1,7 +1,19 @@
-2005-09-20 Release Manager
+2005-09-29 Jakub Jelinek <[EMAIL PROTECTED]>
+
+ PR c++/21983
+ * class.c (find_final_overrider): Move diagnostic about no unique final
+ overrider to...
+ (update_vtable_entry_for_fn): ... here.
+
+2005-09-27 Release Manager
* GCC 4.0.2 released.
+2005-09-21 Mark Mitchell <[EMAIL PROTECTED]>
+
+ PR c++/23993
+ * init.c (integral_constant_value): Use DECL_INTEGRAL_CONSTANT_VAR_P.
+
2005-09-16 Mark Mitchell <[EMAIL PROTECTED]>
PR c++/23914
--
Dr. Ulrich Weigand
Linux on zSeries Development
[EMAIL PROTECTED]
