New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Internal: Remove unsafe unaligned memory access - illegal on SPARC #6962
Labels
Comments
oh boy |
jpountz
added a commit
to jpountz/elasticsearch
that referenced
this issue
Jul 22, 2014
This class potentially does unaligned memory access and does not bring much now that we switched to global ords for terms aggregations. Close elastic#6962
Closed
jpountz
changed the title
Remove unsafe unaligned memory access
Core: Remove unsafe unaligned memory access
Jul 23, 2014
jpountz
added a commit
that referenced
this issue
Jul 23, 2014
This class potentially does unaligned memory access and does not bring much now that we switched to global ords for terms aggregations. Close #6962
I added the labels for |
clintongormley
changed the title
Core: Remove unsafe unaligned memory access
Internal: Remove unsafe unaligned memory access - illegal on SPARC
Jul 23, 2014
jpountz
added a commit
that referenced
this issue
Jul 23, 2014
This class potentially does unaligned memory access and does not bring much now that we switched to global ords for terms aggregations. Close #6962
jpountz
added a commit
that referenced
this issue
Jul 23, 2014
This class potentially does unaligned memory access and does not bring much now that we switched to global ords for terms aggregations. Close #6962
ES 1.3.4 still has issues, but this time in lzf compression codec. See file hs_err_pid26623.log at |
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
This class potentially does unaligned memory access and does not bring much now that we switched to global ords for terms aggregations. Close elastic#6962
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
This class potentially does unaligned memory access and does not bring much now that we switched to global ords for terms aggregations. Close elastic#6962
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unaligned memory access is illegal on several architectures (such as SPARC, see https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/elasticsearch/Nh-kXI5J6Ek/WXIZKhhGVHkJ for context).
The text was updated successfully, but these errors were encountered: