Announcement

Collapse
No announcement yet.

Compilation Times, Binary Sizes For GCC 4.2 To GCC 4.8

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • #16
    Guys, don't talk about compile time not being important unless you're a developer and what you're working on is a multi-GB sized project (yes, binary executables, libraries and such, and no data/source code). I've spent one day just recompiling a tiny portion of a project for internal release and usage. About 40 MB (in release) in 8 different versions. Now imagine compiling something about 100 times larger than that, and luckily only in two versions. Obviously, a large portion of this is rarely rebuilt at all, but just copied from central storage, and you only rebuild as small portion of the software as possible, but still, there's a reason for having nightly builds and such. It saves a huge amount of time for developers.

    ... so yeah, compile time matters a lot.

    Oh, and I have a quadcore i7@3.4GHz. Stuff can be compiled fast, but still not at all fast enough.
    Last edited by AHSauge; 03-18-2013, 12:20 PM.

    Comment


    • #17
      Originally posted by Ericg View Post
      You are obviously NOT a developer. If I'm coding and I make 1 change and I re-compile to test it, I'd rather not have to think to myself "Well....I'm gonna be here for a while." For release builds code-speed may be more important, but for test builds? A 10-second kernel build? i would be beyond happy. Itd be like a free hardware upgrade to me haha
      It's quite obvious that we work differently.
      Do you seriously stare at your screen while the compiler is doing work?
      Or can't you write makefiles so that you have to rebuild everything every time you touch a file?
      Compiling is background work for me. I NEVER wait for compilation to finish. I do actual WORK while waiting.
      Every build system I have built or used will not rebuild stuff that does not need rebuilding.
      Even extremely large code projects will usually take a minute or so to generate new binary images if I want to try something out.
      Clean compilations I usually do overnight, lunch, breaks etc.

      GCC's compilation speed is not a problem.
      I'd still give an arm and an leg for something that is 10% faster on average, even if it's 10 times slower.
      Don't believe me? Ask anyone who is building or using anything that is computational intensive.

      Comment


      • #18
        Originally posted by Ericg View Post
        make -j4 on a i5 dualcore at 1.6ghz can take hours, yes. It sucks -.-
        You're doing it wrong, -j4 is overkill for a dualcore (even with hyperthreading). -j3 would probably yeld better results. If you also have 1GB of RAM or less -j2 might be even faster.

        Comment

        Working...
        X