You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apache Arrow cpp code does not support power architecture.
While building "Apache Arrow" for cpp for power architecture, it throws below error: "c++: error: unrecognized command line option â-msse3â"
Unable to port it for power.
I was working on this Issue and not able to assign it to myself, I guess due to less permission privilege.
Currently I have fixed this Issue. Please find the details below:
To enable SIMD support(SIMD being feature of best processor) for power architecture for Apache Arrow, needs to replace "sse3" with "altivec" flag in "CMakeLists.txt".
Please find attached patch named "build_powerSupport_patch" for the same to support Apache Arrow cpp for Power Architecture.
Regards,
Sonali Shrivastava
Power Open Source Solutions
To enable SIMD support(SIMD being feature of best processor) for power architecture for Apache Arrow, needs to replace "sse3" with "altivec" flag in "CMakeLists.txt".
I understand it needs to support power arch, but why it has to replace "sse3" with "altivec"? IMO, this should be done intelligently, switching to the other by detecting the underlying CPU arch, please.
Yes, it is not final code commit, it was proposed thing to support "altivec" flag, have not done any code commit yet. Things will be modified later if power support for Apache Arrow is required?
Thank You @xhochy
Apache Arrow cpp code does not support power architecture.
While building "Apache Arrow" for cpp for power architecture, it throws below error: "c++: error: unrecognized command line option â-msse3â"
Unable to port it for power.
Environment: RHEL 7.2 power and Ubuntu 15.10 power architecture
Reporter: sonali shrivastava
Assignee: Uwe Korn / @xhochy
Original Issue Attachments:
Note: This issue was originally created as ARROW-90. Please see the migration documentation for further details.
The text was updated successfully, but these errors were encountered: