I reported it years ago and never heard anything. I don't even know if the bug is still there in more recent releases of gcc. Once I recognized the problem, it was easy to get around by adding do-nothing statements to reference variables whose code was getting optimized out. I also tried to make a small test case to illustrate the problem but this test always worked OK.
If you delete the bug from Ubuntu tracking that is OK with me. regards Mike 2012/3/6 Václav Šmilauer <[email protected]> > Has this bug been reported to gcc developers? In that case, it can be > tracked automatically. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/817768 > > Title: > GCC optimizer removes necessary code > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/817768/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/817768 Title: GCC optimizer removes necessary code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.5/+bug/817768/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
