I couldn't find any info either. As far as I understand, x264 was doing something that wasn't standard-compliant (array overreads), and the GCC optimization aggressive-loop-optimizations relies on the assumption that all code is standard-compliant. So this is not a GCC bug.
It may be possible to verify this with Valgrind, but I think the version of Valgrind in Ubuntu doesn't support all the instructions that x264 uses yet, so this is requires recompilation without assembly optimizations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1241772 Title: Miscompilation with gcc 4.8 (segfault in x264_cqm_init) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x264/+bug/1241772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
