This patch only removes the most obvious pieces of windows code.
There is certainly more windows-related code remaining.

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

Kenneth Raffenetti authored Jan 30, 2014 and Pavan Balaji committed Jan 30, 2014

Change the default name service system from file to pmi. The file
method can be unreliable on network filesystems with client side
caching.

Closes #2007

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Kenneth Raffenetti authored Jan 22, 2014 and Pavan Balaji committed Jan 24, 2014

Fixes errors in commit [5bbfe808].

1. Run config.rpath with each compiler individually, as the syntax
   may differ for passing options through to the linker.

2. Move the rpath flags to just before the mpich library, where they
   are necessary.

Fixes #1044.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Kenneth Raffenetti authored Dec 20, 2013 and Pavan Balaji committed Jan 18, 2014

Simplify logic in compile wrapper scripts. Use configure substitutions
where possible to better match pkg-config style.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Includes the following modifications by Pavan Balaji:

Remove the PAC_COMPILER_SHLIB_FLAGS usage, instead of modifying the
macro in confdb.

The ordering of flags in mpicc and friends does not match that of
pkg-config.  This is because of two reasons.

1. pkg-config reorders flags when it outputs them.  This requires us
to manually adjust the flags in mpicc to match up, and is error prone.

2. mpicc and friends provide LDFLAGS before the user-specified flags,
followed by the include and library directories.  This is to make sure
that the LDFLAGS are listed before the application source file.
Reordering them to match pkg-config loses this flexibility.

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

Kenneth Raffenetti authored Dec 09, 2013 and Pavan Balaji committed Jan 18, 2014

Add rpath flags to pkg-config to match compiler wrappers. Fixes #1044

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Disabling runtime check for thread-safety is not a correct option.
This would cause memory allocation and string manipulation routines to
be unusable before the thread-safety level is set.  Fixes #1900.

Signed-off-by: Michael Blocksome <blocksom@us.ibm.com>
Signed-off-by: Rob Latham <robl@mcs.anl.gov>

Make the default of --enable-mpit-pvars= be 'none' instead of 'all'

Signed-off-by: Junchao Zhang<jczhang@mcs.anl.gov> (Reviewed by Bill Gropp)

Also deleted instr option in configure.ac

Signed-off-by: Junchao Zhang<jczhang@mcs.anl.gov> (Reviewed by Bill Gropp)

Added support to handle --program-suffix and --program-prefix options.

Fixes #1967.

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

Fixes #1965

Signed-off-by: Michael Blocksome <blocksom@us.ibm.com>

In C, left-shift has well-defined behavior, but right-shift does not
for signed integers.  The implementation is free to pad the shifted
bits with 0's or 1's.  In this patch, we type-cast the values to
unsigned integers to make the behavior well-defined.

Signed-off-by: Rob Latham <robl@mcs.anl.gov>

Rob Latham authored Oct 18, 2013 and Pavan Balaji committed Oct 31, 2013

configure determines the right type for MPI_Aint, MPI_Fint, and
MPI_Count, so we have to move the MPIR_Bsend checks later in configure.
Then we can promote a plain int to MPI_Aint.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

When MPI_Count was added to the status field, a bunch of bogus checks
got added into configure and MPI_Init.  This patch cleans up these
checks.

Signed-off-by: William Gropp <wgropp@illinois.edu>

Based on an Intel contributed patch.  The idea is to use the bits from
the cancelled field to extend the count, rather than increasing the
count datatype itself.

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

Fixes to the bit manipulation based on feedback from Artem Yalozo @
Intel.

Fixes to the naming convention based on feedback from Bill Gropp.

Signed-off-by: William Gropp <wgropp@illinois.edu>

This reverts commit 81ad170b

.

Signed-off-by: William Gropp <wgropp@illinois.edu>

Junchao Zhang authored Oct 18, 2013 and Pavan Balaji committed Oct 26, 2013

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Junchao Zhang authored Oct 18, 2013 and Pavan Balaji committed Oct 26, 2013

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

In some cases, MPIR_COUNT_ALIGNMENT was not being defined.  This
fixes that case, which came up when trying the -feature=fint=on option
for the Fortran 77 code.

This was changed to 1024 to give space for larger error strings.  But
this caused an ABI breakage for a number of MPICH partners.  This
patch reverts the size back the size to what we had in older mpich
releases.

An initial version of this patch was contributed by Intel.

Signed-off-by: Ken Raffenetti <raffenet@mcs.anl.gov>

Signed-off-by: Wesley Bland <wbland@mcs.anl.gov>

In general, added weak symbol support for compilers supporting
__attribute__((weak,alias)) instead of #pragma weak.

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>
Signed-off-by: William Gropp <wgropp@illinois.edu>

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

Fixes #1695

Signed-off-by: Pavan Balaji <balaji@mcs.anl.gov>

If the device specified a timer type, use that by default.  If none is
specified, configure will try to detect one.  User-specified types are
always given priority.

Signed-off-by: Michael Blocksome <blocksom@us.ibm.com>

The previous patch was meant to allow devices to automatically pick
the default timer type they like.  However, it forces the device to
pick one of the predefined timer types.

If a higher than single or funneled thread level is required and no
thread package is provided, abort.

1. Remove the option for default, since that can be picked with just
--enable-threads without any additional arguments as well.

2. Don't do any device-specific assignments in the top-level
configure.  This is not the right place to do that.  If the device
wants to use a particular thread-level, it should set that in its
subconfigure.m4.

Michael Blocksome authored May 22, 2013 and Pavan Balaji committed Jun 07, 2013

The pamid device does not require a pm and will set the default to 'no'.
This eliminates the requirement to specify the '--with-pm=no' configure
option in order to configure and build successfully.

(includes modifications by Pavan Balaji @ Argonne).

Michael Blocksome authored May 22, 2013 and Pavan Balaji committed Jun 07, 2013

For a bgq configure, this means that the following option is no longer
required to be set:

 --with-cross-file=src/mpid/pamid/cross/bgq8

(with modifications by Pavan Balaji @ Argonne).

configure option.

Reviewed by Charles Archer @ IBM.