[chromium-dev] Re: Has your computer melted?
I've heard it claimed that the reason it's undocumented in VS2005 is
because there are bugs that mean it can do the wrong thing from time
to time--perhaps this is why some people are seeing errors.
It's documented (and supposed to work properly) in VS2008, and I've
been using it for building chromium for many months without any
apparent problems. The ability to do parallel builds of single
projects (rather than merely build projects in parallel) makes it
quite desirable, IMO.
2009/1/6 Brett Wilson bre...@chromium.org:
On Jan 5, 4:32 pm, Brett Wilson bre...@chromium.org wrote:
I just checked in a change to use /MP for all compiles, which is a
secret undocumented flag that does parallel compiles within each
project.
Please let me know of your computer melts or becomes unusable during a
compile. It should more efficiently use all of your CPUs when doing
regular Visual Studio builds (it will have no effect on
IncrediBuilds). You can remove it from essential.vsprops if it's
causing problems.
We tested on Carlos' 2-processor system and it pegged the CPU more,
although it's not clear if it's a lot faster than before. On my
4-processor system, a build of just chrome_exe and all of it's
dependencies went from 25 to 16 minutes after using this flag. So if
you hate IncrediBuild, life might actually be tolerable without it for
fast systems.
This was backed out earlier today due to weird errors, especially with
regard to linking and symbols. Some people have also reported that
Visual Studio can think everything is out of date and rebuilds when
it's not necessary.
If you would like to keep trying this change out, do this locally:
http://chrome-svn/viewvc/chrome/trunk/src/build/internal/essential.vsprops?r1=7533r2=7573
and restart Visual Studio.
Brett
--
char a[9],*p=a;main(c,V)char**V;{char*v=c0?1[V]:V;if(c)for(;(c=*v)93^
c;p+=!(62^c)-!(60^c),*p+=!(43^c)-!(45^c),44^c||read(0,p,1),46^c||putchar(*p)
,91^c||(v=*p?main(-1,v+1),v-1:main(0,v)),++v);else for(;c+=!(91^*v)-!(93^*v)
;++v);return v;} /* drpi...@gmail.combrainf*** program as argv[1] */
--~--~-~--~~~---~--~~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~--~~~~--~~--~--~---
[chromium-dev] Re: Has your computer melted?
I started seeing a slew of: 98glue.lib(autofill_form.obj) : fatal error LNK1318: Unexpected PDB error; RPC (23) '(0x06BA)' 26...\xmemory(155) : error C2471: cannot update program database 'c:\b\slave\try-win32-2\build\src\chrome\debug\obj\plugin_tests\vc80.pdb' 26...\xmemory(155) : error C2471: cannot update program database '??? ' and other neat errors like that on the try slaves. I don't know why but it doesn't seem to happen on the continuous build slaves. Maybe related to IB? Maybe we'll need to revert and folks can enable it locally. On Mon, Jan 5, 2009 at 10:50 PM, Mohamed Mansour m0.interact...@gmail.com wrote: Awesome Brett! My Quad Core processor is using all the 4 CPU :) 94% constant :x Mine took 20minutes to build from scratch, big improvement! I was doing many other stuff at the same time, Java (Eclipse), C# Visual Studio, browsing. Awesome Improvement, thanks! No need to wait 40 minutes :) On Mon, Jan 5, 2009 at 7:32 PM, Brett Wilson bre...@chromium.org wrote: I just checked in a change to use /MP for all compiles, which is a secret undocumented flag that does parallel compiles within each project. Please let me know of your computer melts or becomes unusable during a compile. It should more efficiently use all of your CPUs when doing regular Visual Studio builds (it will have no effect on IncrediBuilds). You can remove it from essential.vsprops if it's causing problems. We tested on Carlos' 2-processor system and it pegged the CPU more, although it's not clear if it's a lot faster than before. On my 4-processor system, a build of just chrome_exe and all of it's dependencies went from 25 to 16 minutes after using this flag. So if you hate IncrediBuild, life might actually be tolerable without it for fast systems. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Has your computer melted?
I got those fatal error LNK. That happens if: - When I stop the build in the middle. - When I code while building I had to just clean that project Build Clean project, and it works. On Tue, Jan 6, 2009 at 2:22 PM, Marc-Antoine Ruel mar...@chromium.orgwrote: I started seeing a slew of: 98glue.lib(autofill_form.obj) : fatal error LNK1318: Unexpected PDB error; RPC (23) '(0x06BA)' 26...\xmemory(155) : error C2471: cannot update program database 'c:\b\slave\try-win32-2\build\src\chrome\debug\obj\plugin_tests\vc80.pdb' 26...\xmemory(155) : error C2471: cannot update program database '??? ' and other neat errors like that on the try slaves. I don't know why but it doesn't seem to happen on the continuous build slaves. Maybe related to IB? Maybe we'll need to revert and folks can enable it locally. On Mon, Jan 5, 2009 at 10:50 PM, Mohamed Mansour m0.interact...@gmail.com wrote: Awesome Brett! My Quad Core processor is using all the 4 CPU :) 94% constant :x Mine took 20minutes to build from scratch, big improvement! I was doing many other stuff at the same time, Java (Eclipse), C# Visual Studio, browsing. Awesome Improvement, thanks! No need to wait 40 minutes :) On Mon, Jan 5, 2009 at 7:32 PM, Brett Wilson bre...@chromium.org wrote: I just checked in a change to use /MP for all compiles, which is a secret undocumented flag that does parallel compiles within each project. Please let me know of your computer melts or becomes unusable during a compile. It should more efficiently use all of your CPUs when doing regular Visual Studio builds (it will have no effect on IncrediBuilds). You can remove it from essential.vsprops if it's causing problems. We tested on Carlos' 2-processor system and it pegged the CPU more, although it's not clear if it's a lot faster than before. On my 4-processor system, a build of just chrome_exe and all of it's dependencies went from 25 to 16 minutes after using this flag. So if you hate IncrediBuild, life might actually be tolerable without it for fast systems. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Has your computer melted?
On Jan 5, 4:32 pm, Brett Wilson bre...@chromium.org wrote: I just checked in a change to use /MP for all compiles, which is a secret undocumented flag that does parallel compiles within each project. Please let me know of your computer melts or becomes unusable during a compile. It should more efficiently use all of your CPUs when doing regular Visual Studio builds (it will have no effect on IncrediBuilds). You can remove it from essential.vsprops if it's causing problems. We tested on Carlos' 2-processor system and it pegged the CPU more, although it's not clear if it's a lot faster than before. On my 4-processor system, a build of just chrome_exe and all of it's dependencies went from 25 to 16 minutes after using this flag. So if you hate IncrediBuild, life might actually be tolerable without it for fast systems. This was backed out earlier today due to weird errors, especially with regard to linking and symbols. Some people have also reported that Visual Studio can think everything is out of date and rebuilds when it's not necessary. If you would like to keep trying this change out, do this locally: http://chrome-svn/viewvc/chrome/trunk/src/build/internal/essential.vsprops?r1=7533r2=7573 and restart Visual Studio. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
[chromium-dev] Re: Has your computer melted?
Awesome Brett! My Quad Core processor is using all the 4 CPU :) 94% constant :x Mine took 20minutes to build from scratch, big improvement! I was doing many other stuff at the same time, Java (Eclipse), C# Visual Studio, browsing. Awesome Improvement, thanks! No need to wait 40 minutes :) On Mon, Jan 5, 2009 at 7:32 PM, Brett Wilson bre...@chromium.org wrote: I just checked in a change to use /MP for all compiles, which is a secret undocumented flag that does parallel compiles within each project. Please let me know of your computer melts or becomes unusable during a compile. It should more efficiently use all of your CPUs when doing regular Visual Studio builds (it will have no effect on IncrediBuilds). You can remove it from essential.vsprops if it's causing problems. We tested on Carlos' 2-processor system and it pegged the CPU more, although it's not clear if it's a lot faster than before. On my 4-processor system, a build of just chrome_exe and all of it's dependencies went from 25 to 16 minutes after using this flag. So if you hate IncrediBuild, life might actually be tolerable without it for fast systems. Brett --~--~-~--~~~---~--~~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~--~~~~--~~--~--~---
