Ralph Castain 5d14fa7546 Fix mpi_abort, minimize error output. ...

This commit was SVN r26266.

2012-04-11 14:37:08 +00:00

..

base.h

Sorry for mid-day commit, but I had promised on the call to do this upon my return.

2012-04-06 14:23:13 +00:00

ess_base_close.c

- On the way to get the BTLs split out and lessen dependency on orte:

2009-02-14 02:26:12 +00:00

ess_base_fns.c

Sorry for mid-day commit, but I had promised on the call to do this upon my return.

2012-04-06 14:23:13 +00:00

ess_base_get.c

Add a resilience to ORTE. Allows the runtime to continue after a process (or

2011-06-23 20:38:02 +00:00

ess_base_open.c

Sorry for mid-day commit, but I had promised on the call to do this upon my return.

2012-04-06 14:23:13 +00:00

ess_base_put.c

Remove unused include files

2011-02-16 00:32:47 +00:00

ess_base_select.c

Sorry for mid-day commit, but I had promised on the call to do this upon my return.

2012-04-06 14:23:13 +00:00

ess_base_std_app.c

Fix mpi_abort, minimize error output.

2012-04-11 14:37:08 +00:00

ess_base_std_orted.c

Sorry for mid-day commit, but I had promised on the call to do this upon my return.

2012-04-06 14:23:13 +00:00

ess_base_std_prolog.c

This is actually a much smaller commit than it appears at first glance - it just touches a lot of files. The --without-rte-support configuration option has never really been implemented completely. The option caused various objects not to be defined and conditionally compiled some base functions, but did nothing to prevent build of the component libraries. Unfortunately, since many of those components use objects covered by the option, it caused builds to break if those components were allowed to build.

2011-11-22 21:24:35 +00:00

ess_base_std_tool.c

Sorry for mid-day commit, but I had promised on the call to do this upon my return.

2012-04-06 14:23:13 +00:00

help-ess-base.txt

Merge the ORTE devel branch into the main trunk. Details of what this means will be circulated separately.

2008-02-28 01:57:57 +00:00

Makefile.am

Complete implementation of the ess.proc_get_locality API. Up to this point, the API was only capable of telling if the specified proc was sharing a node with you. However, the returned value was capable of telling you much more detailed info - e.g., if the proc shares a socket, a cache, or numa node. We just didn't have the data to provide that detail.

2011-10-19 20:18:14 +00:00