On 11/11/14 03:23, Scott Duplichan wrote: > Jordan Justen [mailto:[email protected]] wrote: > > ]To contradict my request for separate patches for each package, I do > ]think this is a case where a single patch makes more sense even though > ]it touches multiple packages. > ] > ]I don't really find the NOOPT target very interesting. I think we > ]don't actually gain much with NOOPT since it can't often be used on > ]firmware images. > > The NOOPT build is almost a necessity for source level debugging > a Microsoft build. With it, local variables are visible and accurate > for every single step. With an optimized build, some locals are > eliminated entirely and others are kept in registers, something the > Microsoft debug information doesn't track. > > During the transition from legacy BIOS to UEFI, the projects I worked > on were limited to 1MB flash, the max size for LPC chips used on > reference boards at the time. We had to make do with enabling debug > info for the optimized build during that period. Servers are less > likely to have a flash space limitation that prevents NOOPT build > use. The last server project I worked on used a 16MB flash chip. > Don't today's desktop boards have 4-8 MB of flash? That should > hold a NOOPT build.
What's wrong with simply using DEBUG then? Thanks Laszlo ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
