1 |
Unlikely you screwed up, -O0 makes bigger code than -O2 almost in every |
2 |
case; then -g annotates it. I'm expecting -ggdb to take some few GBs more. |
3 |
|
4 |
It'll be the same if not worse with almost all software, -g3 would make it |
5 |
even worse. |
6 |
|
7 |
|
8 |
Diego Elio Pettenò — Flameeyes |
9 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |
10 |
|
11 |
|
12 |
On Fri, Aug 2, 2013 at 9:05 AM, Michał Górny <mgorny@g.o> wrote: |
13 |
|
14 |
> Dnia 2013-08-02, o godz. 02:07:18 |
15 |
> Duncan <1i5t5.duncan@×××.net> napisał(a): |
16 |
> |
17 |
> > Michał Górny posted on Thu, 01 Aug 2013 13:33:48 +0200 as excerpted: |
18 |
> > |
19 |
> > > LLVM has peek build space consumption around: |
20 |
> > > |
21 |
> > > - 400-550M without clang (depending on targets), |
22 |
> > > - 950-1200M with clang, |
23 |
> > > - 16G with clang & USE=debug (assertions, checks). |
24 |
> > |
25 |
> > Ouch! |
26 |
> > |
27 |
> > Thanks for the heads-up. I didn't realize -g/debug added THAT much! For |
28 |
> > sure I'll have to keep that in mind if I ever decide to build llvm with |
29 |
> > debug... and the general rule in mind for building anything else with |
30 |
> > debug. |
31 |
> |
32 |
> Just to make it clear, USE=debug doesn't imply -g. It gets 16G with |
33 |
> -O2. Curious enough, -O0 -g gave me 14G but maybe I screwed something |
34 |
> up :). |
35 |
> |
36 |
> -- |
37 |
> Best regards, |
38 |
> Michał Górny |
39 |
> |