On 3 January 2012 15:02, Markus Henschel wrote: > My second question is if it makes any sense to submit this bug if it's against gcc version 4.2.4. I still have to use this compiler version but the bug seems to have vanished in version 4.3.3. Is 4.2.4 still maintained? No, as shown on the gcc.gnu.org home page, the oldest maintained release series is GCC 4.4