Unity builds lurked into the Firefox Build System
serge-sans-paille.github.io
Unity builds lurked into the Firefox Build System
1–10 of 64 posts
Re: Unity builds lurked into the Firefox Build System
#2Why can’t static analyzers analyze the main cpp that #include-s the actual code? I don’t understand that point.
And what were the resulting affects on build times?
Re: Unity builds lurked into the Firefox Build System
#3This used to be mandatory for nvcc/CUDA, if you had multiple source files (not just headers) you had to #include all of them in your main file. It made me very uncomfortable.
Re: Unity builds lurked into the Firefox Build System
#4Compilation units are a relic of a time where computers only had a few KB of memory. At this point computers are fast enough and have enough memory to compile the whole thing in one go faster than whatever gains doing change detection and linking will have.
Re: Unity builds lurked into the Firefox Build System
#5Compilation units are a relic of a time where computers only had a few KB of memory. At this point computers are fast enough and have enough memory to compile the whole thing in one go faster than whatever gains doing change detection and linking will have.
This, is just deeply untrue. Do you really think everybody working on compilers and linkers are deeply ignorant? I can easily saturate my 64 GB RAM home setup during a compile.
Re: Unity builds lurked into the Firefox Build System
#6Compilation units are a relic of a time where computers only had a few KB of memory. At this point computers are fast enough and have enough memory to compile the whole thing in one go faster than whatever gains doing change detection and linking will have.
Yeah, no. To this day Firefox developers building Gecko need a beefy desktop machine to be able to do it in a reasonable amount of time. I could do a clean build in 6 minutes with a ThreadRipper whose cores were all pegged, but forget doing the same in under an hour on a laptop.
And that was with unified builds enabled.
Re: Unity builds lurked into the Firefox Build System
#7"Lurked into"?
You can lurk but surely you can't lurk into something?
Re: Unity builds lurked into the Firefox Build System
#8Note that this is not referring to the Game Engine Unity. It's just referring to #including .cpp files.
Re: Unity builds lurked into the Firefox Build System
#9Why can’t static analyzers analyze the main cpp that #include-s the actual code? I don’t understand that point. And what were the resulting affects on build times?
They can. In addition to that, they get confused by a .cpp that isn't the top level file of a compilation unit.
Re: Unity builds lurked into the Firefox Build System
#10"Lurked into"? You can lurk but surely you can't lurk into something?
I assume the author is not a native speaker based on some of the odd grammar and phrasing in the post. It doesn't really detract from the work
Edit: They appear to be french: http://serge.liyun.free.fr/serge/