[mpir-devel] Re: What still needs to be done?

2009-01-09 Thread Bill Hart
It should be easy to verify if it is an issue or not. Until then it should remain a blocker. I'll check the test function. Bill. 2009/1/10 mabshoff : > > > > On Jan 9, 4:59 pm, Bill Hart wrote: >> I've added a ticket for the memory leak. > > Yeah, I saw the ticket. I am not 100% sure this isn'

[mpir-devel] Re: What still needs to be done?

2009-01-09 Thread mabshoff
On Jan 9, 4:59 pm, Bill Hart wrote: > I've added a ticket for the memory leak. Yeah, I saw the ticket. I am not 100% sure this isn't a false positive since the C++ runtime could be involved here and that some times leads to issues. Either way, I wouldn't consider it a blocker since it has been

[mpir-devel] Re: What still needs to be done?

2009-01-09 Thread Bill Hart
I've added a ticket for the memory leak. On Jan 10, 12:41 am, mabshoff wrote: > On Jan 9, 4:05 pm, Bill Hart wrote: > > > OK, I see Jason already fixed the make tune issue. So perhaps the > > nails issue is all that is left. > > > On Jan 9, 11:28 pm, Bill Hart wrote: > > > > I've added the mis

[mpir-devel] Re: What still needs to be done?

2009-01-09 Thread mabshoff
On Jan 9, 4:05 pm, Bill Hart wrote: > OK, I see Jason already fixed the make tune issue. So perhaps the > nails issue is all that is left. > > On Jan 9, 11:28 pm, Bill Hart wrote: > > > I've added the missing gcd prototypes to gmp-impl.h. > > > What else do we need to do before release? > > >

[mpir-devel] Re: What still needs to be done?

2009-01-09 Thread Bill Hart
OK, I see Jason already fixed the make tune issue. So perhaps the nails issue is all that is left. On Jan 9, 11:28 pm, Bill Hart wrote: > I've added the missing gcd prototypes to gmp-impl.h. > > What else do we need to do before release? > > * fix make tune > > * fix nails = 2 > > Anything else?