Ah, I got it. http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Atomic-
Builtins.html says that gcc would accept any data type of 1, 2, 4, or 8
bytes for __sync_lock_test_and_set(), but it turns out that "char" (as
Alex originally committed for bug 497331) doesn't work on the Pandas. I
switched it to int now and also used __sync_lock_release() to comply to
the API, and it works fine now.
** Changed in: postgresql-9.1 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/904828
Title:
Tests fail on armel/panda
To manage notifications about this bug go to:
https://bugs.launchpad.net/linaro-ubuntu/+bug/904828/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
