[mpich2-dev] [mpich-discuss] Overflow in MPI_Aint

[Pavan Balaji]

Joe,

Sure. We also did a bunch of commits on ticket #393 
(http://trac.mcs.anl.gov/projects/mpich2/ticket/393) that might affect 
you as well (hopefully making it easier for you). But we can deal with 
that later.

  -- Pavan

On 07/23/2009 01:20 PM, Joe Ratterman wrote:
> Yes, I can get you the latest patch set soon.  The ones I normally send 
> you guys are built from the special SVN-import I do, so they contain far 
> fewer changes than the patch files that are part of our distribution.  I 
> am working on the 1.1.1 upgrade.  Maybe I can send the patches after I 
> get that working?  That will make it easier to pick out the changes we made.
> 
> Thanks,
> Joe Ratterman
> 
> On Thu, Jul 23, 2009 at 1:07 PM, Pavan Balaji <balaji at mcs.anl.gov 
> <mailto:balaji at mcs.anl.gov>> wrote:
> 
>     Hi Joe,
> 
>     I tried to extract the code change portions from the patch you sent,
>     but that doesn't seem to be easy (the patch seems to show many
>     changes to the docs and other such files which have not changed for
>     a long time). Is there a way for me to get the code changes, either
>     from this patch, or by exporting from some git branch?
> 
>      -- Pavan
> 
> 
>     On 07/21/2009 03:38 PM, Pavan Balaji wrote:
> 
>         Joe,
> 
>             There are a number of MPI_Aint changes that are not in 1.1.
>              For example, there is a block of changes in configure.in
>             <http://configure.in> that relates to this, and it is only
>             in the BGP version.
> 
> 
>         I'm shifting this part of the discussion to mpich2-dev, since
>         it's more developer oriented.
> 
>         In the top-level configure, the MPIR_Pint stuff should be in
>         1.1.1. With respect to the MPI_OFFSET_TYPE part, is there a need
>         for this? This is cross-compile safe, as far as I can tell
>         (there have been some cleanups in the trunk, but this part
>         should be correct even in 1.1). Could you explain this a bit more?
> 
>         With respect to the rest of the patch, a lot of it seems to be
>         based on:
> 
>         1. git-svn differences (e.g., .gitignore files).
> 
>         2. variables that are automatically filled in by svn (e.g.,
>         $Revision$).
> 
>         3. changes in the test suite.
> 
>         Apart from these, I do see a few more changes that need to be
>         integrated. The dcmfd changes should be easy enough to
>         integrate. I'll look into the top-level changes as well.
> 
>          -- Pavan
> 
> 
>     -- 
>     Pavan Balaji
>     http://www.mcs.anl.gov/~balaji
> 
> 

-- 
Pavan Balaji
http://www.mcs.anl.gov/~balaji