** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin18043
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758118
Title:
src/mongo/db/fts/unicode is not optimised on ppc64el
T
Lets close this now that we adopted the Debian patch version 8and
upstream one)
** Changed in: mongodb (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/175
Going back to c#1, though, I can definitely say that using 1 rather than
0 is correct behavior on little-endian machines. The question is
whether this code is being used for big-endian also. If so, then this
change will break the code on big-endian machines. This code needs to
be endian-aware.
I wrote a very small code that mimics this problem, it is at:
https://github.com/leitao/altivec
I found that the information we are looking for (i.e, the bitmap) is at
the second half of the vector, i.e, vec_extract(VSR, 1) will return the
correct value of the output of the perm value, and vec
There was a bug in GCC that could cause incorrect code to be generated
for -mcpu=power8 in a computation involving vec_vbpermq. See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84033.
This bug has been fixed and backported to supported releases (GCC 6 and
7). Please ensure that your toolchain te
** Tags added: architecture-ppc64le bugnameltc-166135 severity-medium
targetmilestone-inin---
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758118
Title:
src/mongo/db/fts/unicode is not optimised o
** Tags added: ppc64el
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758118
Title:
src/mongo/db/fts/unicode is not optimised on ppc64el
To manage notifications about this bug go to:
https://bugs.l
I'm wary of the suggested change in the upstream bug report:
-return vec_extract(vec_vbpermq(_data, bits), 0);
+return vec_extract(vec_vbpermq(_data, bits), 1);
It's useful to know if this fixes the problem, and I can confirm that it
does. But without knowing _why_ this fixes the
