Skip to content
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

configure: assembler stdout incorrect (cosmetic issue only) #3036

Closed
rhc54 opened this issue Feb 26, 2017 · 2 comments
Closed

configure: assembler stdout incorrect (cosmetic issue only) #3036

rhc54 opened this issue Feb 26, 2017 · 2 comments
Labels
Milestone

Comments

@rhc54
Copy link
Contributor

rhc54 commented Feb 26, 2017

I'm seeing an incorrect identification of the hardware architecture (similar to issue reported on master #3032):

*** Assembler
checking dependency style of gcc... gcc3
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking for fgrep... /usr/bin/grep -F
checking if .proc/endp is needed... no
checking directive for setting text section... .text
checking directive for exporting symbols... .globl
checking for objdump... objdump
checking if .note.GNU-stack is needed... yes
checking suffix for labels... :
checking prefix for global symbol labels... 
checking prefix for lsym labels... .L
checking prefix for function in .type... @
checking if .size is needed... yes
checking if .align directive takes logarithmic value... no
checking if processor supports x86_64 16-byte compare-and-exchange... yes
checking if compiler correctly handles volatile 128bits... yes
checking if gcc supports GCC inline assembly... yes
checking if gcc supports DEC inline assembly... no
checking if gcc supports XLC inline assembly... no
checking for assembly format... default-.text-.globl-:--.L-@-1-0-1-1-1
checking for assembly architecture... AMD64
checking for builtin atomics... BUILTIN_NO
checking for pre-built assembly file... no (atomic-amd64-linux.s not found)
checking whether possible to generate assembly file... yes
checking for atomic assembly filename... atomic-local.s

This was on an Intel x86_64 box.

@rhc54 rhc54 added this to the v2.1.0 milestone Feb 26, 2017
ggouaillardet added a commit to ggouaillardet/ompi that referenced this issue Feb 27, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used

Fixes open-mpi#3032
Refs open-mpi#3036

Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
ggouaillardet added a commit to ggouaillardet/ompi that referenced this issue Feb 27, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used

Fixes open-mpi#3032
Refs open-mpi#3036

Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>

(cherry picked from commit open-mpi/ompi@2f4013c)
ggouaillardet added a commit to ggouaillardet/ompi that referenced this issue Feb 27, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used

Fixes open-mpi#3032
Refs open-mpi#3036

Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>

(cherry picked from commit open-mpi/ompi@2f4013c)
@jsquyres
Copy link
Member

Per the discussion on #3039, this feels like a cosmetic issue, not something that is actually doing the Wrong Thing on the back-end. Defer to v2.1.1.

@jsquyres jsquyres modified the milestones: v2.1.1, v2.1.0 Feb 27, 2017
@jsquyres jsquyres changed the title Assembler configure for v2.1.0rc1 broken configure: assembler stdout incorrect (cosmetic issue only) Mar 1, 2017
bosilca pushed a commit to bosilca/ompi that referenced this issue Mar 7, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used

Fixes open-mpi#3032
Refs open-mpi#3036

Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
markalle pushed a commit to markalle/ompi that referenced this issue Apr 5, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used

Fixes open-mpi#3032
Refs open-mpi#3036

Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
@hppritcha hppritcha modified the milestones: v2.1.2, v2.1.1 Apr 24, 2017
@rhc54
Copy link
Contributor Author

rhc54 commented May 16, 2017

resolved by @ggouaillardet

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

3 participants