Hi, This was in fact a compiler bug. It has been reported at http://gcc.gnu.org/PR29631 . The bug does not occur with gcc 4.2 anymore. However, it is quite unlikely that it is going to be fixed in the 4.1 series, so the workaround will have to stay in place for now.
--
Falk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
