You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Georgios Kasapoglou (JIRA)" <ji...@apache.org> on 2015/05/15 12:50:00 UTC
[jira] [Commented] (HADOOP-11505)
hadoop-mapreduce-client-nativetask fails to use x86 optimizations in some
cases
[ https://issues.apache.org/jira/browse/HADOOP-11505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545294#comment-14545294 ]
Georgios Kasapoglou commented on HADOOP-11505:
----------------------------------------------
Hello,
instead of doing calculations, can we use gcc's:
val=__builtin_bswap32 (val);
and
val=__builtin_bswap64(val);
It is supposed to work on any architecture. Is that wrong? I've used it and compilation was successful, and it seems to work on T1/sparc.
> hadoop-mapreduce-client-nativetask fails to use x86 optimizations in some cases
> -------------------------------------------------------------------------------
>
> Key: HADOOP-11505
> URL: https://issues.apache.org/jira/browse/HADOOP-11505
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Colin Patrick McCabe
> Assignee: Colin Patrick McCabe
> Labels: BB2015-05-TBR
> Attachments: HADOOP-11505.001.patch
>
>
> hadoop-mapreduce-client-nativetask fails to use x86 optimizations in some cases. Also, on some alternate, non-x86, non-ARM architectures the generated code is incorrect. Thanks to Steve Loughran and Edward Nevill for finding this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)