I'm fine with bumping up the minimum version of flex required. I just want to
have a clue what to bump it up *to*. :-)
If you're confident that 2.5.33 is a good number, that's probably good enough
for me.
Can you find someone at ORNL to commit? I think that this would be fine on the
trunk a
Alex,
It looks like there is a mismatch between what you propose to achieve and the
text in your RFC. You propose to add a new single-process checkpoint-restart
mechanism (MTCP), to the ones already provided in Open MPI. However, most of
the text in your RFC is about DMTCP, which is another lay
I don't know if it works with 2.5.4 for sure but I have seen lexer files that
handle differences between 2.5.4 and 2.5.33 and they don't handle %option noun
put differently. I would assume it will work. Maybe someone still using 2.5.4
can validate this.
-- Swen
On Oct 6, 2011, at 2:59 PM, Jeff
Terry --
Please add this to the agenda for Oct 18. I'd like to invite Alex and his
advisor to the Oct 18 teleconf to discuss.
On Oct 6, 2011, at 2:58 AM, Alex Brick wrote:
> WHAT: Bring in the mtcp CRS component
>
> WHY: Add support for the MTCP checkpoint/restart service
>
> WHERE: opal/m
Nifty -- I had no idea that %unput existed. Do you know how far back it works
in flex versions? We currently say on the web site that developers need at
least flex 2.5.4 to build. Will using an %unput (say, in trunk and v1.5)
require a new minimum flex version?
On Oct 6, 2011, at 2:55 PM, B
Fwiw I created a patch to get rid of the following warnings:
keyval_lex.c:1251: warning: 'yyunput' defined but not used
show_help_lex.c:1182: warning: 'yyunput' defined but not used
carto_file_lex.c:1256: warning: 'yyunput' defined but not used
util/hostfile/hostfile_lex.c:1665: warning: 'yyunput'
WHAT: Bring in the mtcp CRS component
WHY: Add support for the MTCP checkpoint/restart service
WHERE: opal/mca/crs/mtcp
TIMEOUT: Tuesday teleconf, 2011-10-18 (about 2 weeks from now)
---
What is MTCP?
DMTCP (Distributed MultiThreaded CheckPointing,
htt
