I've done a little more testing, with the following conclusions: - The bug is also present in some older libgcj versions, including in particular libgcj5 3.4.4-5 and libgcj6 4.0.2-6.
- The bug appears to be absent in gcc-snapshot 20051124-1. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
