Skip to content

Improve ARM support #170

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

Closed
ompiteam opened this issue Oct 1, 2014 · 10 comments
Closed

Improve ARM support #170

ompiteam opened this issue Oct 1, 2014 · 10 comments
Assignees
Labels
Milestone

Comments

@ompiteam
Copy link
Contributor

ompiteam commented Oct 1, 2014

Per discussion on the devel list:

http://www.open-mpi.org/community/lists/devel/2013/01/11955.php

Lief would like to revert r27882 and implement it differently (see first mail in this thread). r27882 was not accepted into v1.6; a different (simpler) workaround was used as a stopgap.

Lief -- do you have a timeline for this implementation? Can it be done in the near enough future to include in the v1.7 series? Should be revert r27882 in the immediate future?

@ompiteam ompiteam self-assigned this Oct 1, 2014
@ompiteam ompiteam added this to the Open MPI 1.9 milestone Oct 1, 2014
@ompiteam
Copy link
Contributor Author

ompiteam commented Oct 1, 2014

Imported from trac issue 3481. Created by jsquyres on 2013-01-25T18:57:00, last modified: 2014-04-22T16:01:01

@ompiteam ompiteam added the bug label Oct 1, 2014
@ompiteam
Copy link
Contributor Author

ompiteam commented Oct 1, 2014

Trac comment by phargrov on 2014-01-23 19:38:55:

No progress in 12 months?

The original description indicates that 1.6 used a "different" solution to the ARM asm issues, and asks if r27882 should be reverted (in time for the then-future v1.7). However, the distinct ARMV[567].asm files created in r27882 do not appear in the trunk or v1.7 branch. So, either I am misunderstanding the ticket's Description, or something has changed without an update to the ticket.

I can confirm that the current 1.7.4rc tarballs, configured with no special options, passes "make all install check" on a multi-core armv7 system (Ubuntu Precise on QEMU-emulated Versatile Express).

I also have an armv5 (QEMU-emulated Versatile PB) where I suspect we must fail due to attempts to use strex/ldrex instructions in the asm code (though I've not had time to confirm).

-Paul

yosefe pushed a commit to yosefe/ompi that referenced this issue Mar 5, 2015
Fix a cuda error message when we run out of memory
@jsquyres jsquyres modified the milestones: Future, Open MPI v2.0.0 Jun 24, 2015
@bosilca
Copy link
Member

bosilca commented Jul 7, 2015

Several issues with compiling on a RasberryPi2 (armv7-a) have been reported on the mailing list. The patch proposed in the original svn r27882 provides an ugly but functional solution. I propose we reintegrate the original patch in master.

@jsquyres jsquyres modified the milestones: Open MPI v1.10.0, Future Jul 11, 2015
@jsquyres jsquyres assigned bosilca and unassigned ompiteam Jul 11, 2015
@jsquyres
Copy link
Member

@bosilca Sounds good. Can you commit to master?

@jsquyres jsquyres modified the milestones: Open MPI v1.10.0, Open MPI v1.10.1 Sep 2, 2015
@bosilca
Copy link
Member

bosilca commented Sep 15, 2015

I just got a rpi2. Give me few days to check the status of this.

@jsquyres
Copy link
Member

Move this to the Future milestone -- I think 2.x is the earliest this will happen.

@jsquyres jsquyres modified the milestones: Open MPI v2.x, Open MPI v1.10.1 Oct 13, 2015
@jsquyres jsquyres assigned shamisp and unassigned bosilca Feb 13, 2017
@jsquyres
Copy link
Member

@shamisp Just saw this in the old issues -- can you look to see if it is still relevant? If not, feel free to close it. Thanks.

@hppritcha hppritcha modified the milestones: v3.0.0, v2.x Feb 14, 2017
@hppritcha
Copy link
Member

Moving to 3.x milestone

@hppritcha
Copy link
Member

@shamisp if you want anything for ARM in 3.0.0 needs to be in the pipeline this week. We're planning on forking this week and only what's on #3107 (modulo bug fixes) will get in.

@hppritcha hppritcha added this to the v3.1.0 milestone Mar 14, 2017
@hppritcha hppritcha removed this from the v3.0.0 milestone Mar 14, 2017
@jsquyres
Copy link
Member

I believe that ARMv8 is now well-supported.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants