I've discovered that "-Og" does produce working, somewhat-optimized, code. Still, I need to understand why this code was appearing to the optimizer as a no-op. I need to make sure that no other code is being incorrectly optimized. As it stands, this looks to me to be erroneous optimization by GCC.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909838 Title: gcc -O3 produces invalid code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1909838/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
