Skip to content

master: opal: add support for s390 and s390x architectures #3454

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

Merged
merged 1 commit into from
May 6, 2017

Conversation

nmorey
Copy link
Contributor

@nmorey nmorey commented May 5, 2017

Signed-off-by: Nicolas Morey-Chaisemartin [email protected]

@ompiteam-bot
Copy link

Can one of the admins verify this patch?

@jsquyres jsquyres requested a review from hjelmn May 5, 2017 12:21
@jsquyres
Copy link
Member

jsquyres commented May 5, 2017

@hjelmn @bosilca This is the master version of #3449.

@jsquyres jsquyres changed the title opal: add support for s390 and s390x architectures master: opal: add support for s390 and s390x architectures May 5, 2017
@bosilca
Copy link
Member

bosilca commented May 5, 2017

From what I see in the code there is no practical difference between s390 and s390x from OMPI perspective. I wonder why are we creating 2 defines?

@nmorey
Copy link
Contributor Author

nmorey commented May 5, 2017

It is not completely necessary now but as they are 31 and 64 bit arch, I anticipated some differences that may appear later

Copy link
Member

@bosilca bosilca left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A word about this in the config/opal_config_asm.m4 will be great.

@nmorey nmorey force-pushed the devel/master-s390-support branch from 7976eec to 7bad4fd Compare May 5, 2017 15:16
Signed-off-by: Nicolas Morey-Chaisemartin <[email protected]>
@nmorey nmorey force-pushed the devel/master-s390-support branch from 7bad4fd to b4d9d5e Compare May 5, 2017 15:23
@jsquyres
Copy link
Member

jsquyres commented May 6, 2017

Thanks @nmorey!

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

Successfully merging this pull request may close these issues.

4 participants