On Mon, Sep 23, 2013 at 1:04 PM, Gregory Szorc <g...@mozilla.com> wrote:
> On Sep 22, 2013, at 16:35, Anthony Jones <ajo...@mozilla.com> wrote: > > > On 21/09/13 17:58, Robert O'Callahan wrote: > >> I don't think that's necessarily true on Windows. If we can find a way > to > >> generate Visual Studio projects and use those to build, or do most of > the > >> build, we can probably go a lot faster than using cl command-line > >> invocations compiling one file per invocation. > > > > It would be nice to see multiple files per cl invocation. That would > > likely be a significant win for Windows. The performance improvements > > are good for Linux but Windows build performance still lags many minutes > > behind the Linux. > > Not sure what you mean here. If you use /MP to build multiple files with > one cl.exe, you lose out on /showIncludes and dependencies would be busted. > I observe that Visual Studio builds do not spawn one cl process per translation unit. Knowing how slow Windows is at spawning processes, I suspect the build would be a lot faster if we used a single cl process to compile multiple tranlation units. /MP apparently spawns multiple processes to compile a set of files. That's kind of the opposite of what we want here. I see how compiling several files in the same cl invocation would mess up using /showincludes to track dependencies, making this difficult to fix. The only possibility I can think of for fixing this is to emit a Visual Studio project and make the Visual Studio builder responsible for tracking #include dependencies. Rob -- Jtehsauts tshaei dS,o n" Wohfy Mdaon yhoaus eanuttehrotraiitny eovni le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o Whhei csha iids teoa stiheer :p atroa lsyazye,d 'mYaonu,r "sGients uapr,e tfaokreg iyvoeunr, 'm aotr atnod sgaoy ,h o'mGee.t" uTph eann dt hwea lmka'n? gBoutt uIp waanndt wyeonut thoo mken.o w * * _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
