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

README: Update F08 language about IBM XL compiler #3826

Merged
merged 1 commit into from
Jul 11, 2017
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions README
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ Copyright (c) 2006-2017 Cisco Systems, Inc. All rights reserved.
Copyright (c) 2006-2011 Mellanox Technologies. All rights reserved.
Copyright (c) 2006-2012 Oracle and/or its affiliates. All rights reserved.
Copyright (c) 2007 Myricom, Inc. All rights reserved.
Copyright (c) 2008-2016 IBM Corporation. All rights reserved.
Copyright (c) 2008-2017 IBM Corporation. All rights reserved.
Copyright (c) 2010 Oak Ridge National Labs. All rights reserved.
Copyright (c) 2011 University of Houston. All rights reserved.
Copyright (c) 2013-2015 Intel, Inc. All rights reserved
Expand Down Expand Up @@ -183,8 +183,13 @@ Compiler Notes
source directory path names that was resolved in 9.0-4 (9.0-3 is
known to be broken in this regard).

- IBM's xlf compilers: NO known good version that can build/link
the MPI f08 bindings or build/link the OpenSHMEM Fortran bindings.
- OpenSHMEM Fortran bindings do not support the `no underscore` Fortran
symbol convention. IBM's xlf compilers build in that mode by default.
As such, IBM's xlf compilers cannot build/link the OpenSHMEM Fortran
bindings by default. A workaround is to pass FC="xlf -qextname" at
configure time to force a trailing underscore. See the issue below
for more details:
https://github.com/open-mpi/ompi/issues/3612

- On NetBSD-6 (at least AMD64 and i386), and possibly on OpenBSD,
libtool misidentifies properties of f95/g95, leading to obscure
Expand Down