> -----Original Message----- > From: Sun Chan [mailto:sun.c...@gmail.com] > Sent: Monday, April 02, 2012 5:39 PM > To: Gilmore, Doug > Cc: open64-devel > Subject: Re: [Open64-devel] review request -- CG > > looks fine with ebo fix. Thanks! > for the other fix, shouldn't that be inside > x8664? Or at least inside ifdef? > Sun Note that the file being changed is:
osprey/be/cg/x8664/cg_sched.cxx So it is architecture specific. Doug > > On Tue, Apr 3, 2012 at 8:34 AM, Gilmore, Doug <doug.gilm...@amd.com> > wrote: > > This patch fixes initializations of several MEM_POOLs in > > ebo_special.cxx, which eliminates many memory pool initialization > > trace warnings when the compiler is built in debug mode. > > > > Could a gatekeeper review this change when they have a chance? > > > > Thanks, > > > > Doug > > > > --------------------------------------------------------------------- > --------- > > Better than sec? Nothing is better than sec when it comes to > > monitoring Big Data applications. Try Boundary one-second > > resolution app monitoring today. Free. > > http://p.sf.net/sfu/Boundary-dev2dev > > _______________________________________________ > > Open64-devel mailing list > > Open64-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/open64-devel > > ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Open64-devel mailing list Open64-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/open64-devel
