Hi Igor, Good start! what IPF commit criteria looks reasonable for you? Is "IPF build is compilable" criteria enough?
On 10/20/06, Igor Chebykin <[EMAIL PROTECTED]> wrote:
Hello all, I suggest a short series of patches for drlvm ipf code generator. We have some improvements for jitrino/ipf and would like to commit its to harmony. All patches will change only vm/jitrino/src/codegenerator/ipf/* files, therefore ia32 remains OK. The first patch is about 67k size and contains following files: IpfCfg.h, IpfCfg.cpp methods added in Edge and Node classes IpfCodeLayouter.h, IpfCodeLayouter.cpp new BotomUp algorithm implementation IpfEmitter.h, IpfEmitter.cpp minor changes in logging, Emitter::registerDirectCall() and debugging support IpfIrPrinter.h, IpfIrPrinter.cpp added method to print Node chains IpfType.h types to support Node chains added IpfCfgVerifier.cpp method cfg.getArgs() deprecated IpfInst.cpp methods to identify inst kind added (isBr, isCall …) IpfRegisterAllocator.cpp minor changes in logging Thanks, Igor. -- Igor Chebykin, Intel Middleware Products Division --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Mikhail Fursov
