here is an updated patch for this bug. I'm not sure if the upstream code has changed in the meantime, but I found a couple more uses of 'mov pc' in the code that I've also patched. Is that what was meant by this being "incomplete"?
I've also touched it up to be mergeable with Debian (support v4t builds with #ifdef). Confirmed that installing the resulting klibc packages on my beagleboard gives me a successfully-booting initramfs with klibc; and the vfork/setjmptest test cases all pass in the klibc package tree. We may yet want to move away from klibc on arm, but I don't see any reason not to apply this fix (and push to Debian)? ** Attachment added: "arm-thumb2" https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/527720/+attachment/1855061/+files/arm-thumb2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/527720 Title: thumb2 porting issues identified: klibc uses mov.*pc -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
