public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: V.Haisman@sh.cvut.cz To: gcc-gnats@gcc.gnu.org Subject: c/7812: insane compilation times Date: Mon, 02 Sep 2002 09:46:00 -0000 [thread overview] Message-ID: <200209021644.g82Gidu4085139@logout.sh.cvut.cz> (raw) >Number: 7812 >Category: c >Synopsis: insanely long compilation times on simple C files >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Mon Sep 02 09:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: U-AMBER2\wilx >Release: 3.3 20020901 (experimental) >Organization: >Environment: System: CYGWIN_NT-5.1 AMBER2 1.3.12(0.54/3/2) 2002-07-06 02:16 i686 unknown host: i686-pc-cygwin build: i686-pc-cygwin target: i686-pc-cygwin configured with: ../srcdir/configure --enable-languages=c,c++ --enable-threads=posix --enable-version-specific-runtime-libs --enable-shared --enable-dwarf2 --with-cpu=athlon-tbird --with-arch=athlon-tbird --srcdir=/C/WilX/gcc33/srcdir >Description: GCC is unable to compile this simple file in reasonable time. In fact I stopped it after one hour. Compiler does not use unreasonable amounts of memory, only around 40MB. >How-To-Repeat: begin 666 gdfontl.i.bz2 M0EIH.3%!62936<&^#LT`T8A?@$00011S2@4$4`HOX=ZJ8!$>\"^UE%$6%9)" M33111K0";`4F66TJ)2IHT&V`%X,9-,@9-#(,C3`C!))$>1E&0:&C(:&:0QDT MR!DT,@R-,",$GJJJ,@P@#``",$U*IJFADT:#(:8@!@*FJIJ33TF(:#$-``.7 M"SV^H!MX\KA5<M!.36SB$:FVI9#48TFQC)3):DTLDS6HQF%1HT5&D9%D!DI$ M:F+%1-DE1,V!#,+*13,-DHV;2B1-BT8-%%F&M8-MHM8HM&9J&T6U;"K95L0M M+23,-LHTFBV&2S;452LV8(F&TB:L6K%K58MK9E#.)R./4N7AT[;S\8P!YOQ^ MN>V0'ITJ)#)*JME3*JT&M5:158BQ6DQ5%C&R3:61A89"V)FV:M*9*TE:JR82 ML&%I5EBIFK0*6$E9:E6J&I:UDF*R6+632BAK:M3&A818S36TPVJH&1DE,:I6 M5E,94K18UFQ#6JR95M!&LEFEK4J6RFQ(QI#)C(SX?GY_3_<^FYG1.-[,VSVS M#.^;9LY3#90S4&U*V4-E,-38;*;9JU&P18QIHJ2QA7TW&2N,C91LDC6HJV@V MU8VM:C:3(:-141BP:9B$@P82+"4`B2$I&92!DQ58VC$5K%6L:K92-J)6U%L1 M-BIM"02&Q:$&,5@T:44:$EJ6MMI`5M))-;96P5L%K&$L-)5,@@(P4&JA#1MH MK&M!41(5DU)BL)6+:""BL2Q6VBR!6%!$14++926T39$$9LM6A1%9*6%111%% M&PE2V$01,@C6DRE8VI+4%4C)-BM)A%2::DMFTVPUEM+,M9D*V2$BK6FRQ6A8 ML4HUBC6+4VC4;!8TS6I9LV6Q*20:+3-),:*@+,FK65M*JV*V%1M"V39)-2(H MA@F0F08P@&4F,DDF$RM;&VT*VQ6VRAE#&5A1E;;4;;":L;%;,#&M!1K1:Q:R M`2TR"LM2532C1J905-ILM-L;%8R3*P:FJ6:MJ8IM:*J,)%))3:(4%DU%1M&V MDHT5FI#"I(L:-D&5*6R2TF1LIDLR6M;-DR9-DJPI-IIFA:FS9,IAI`29)J-9 MJ8L-FJHK!M&RRI8R(VP:VHVC56M2-BIM4-@FRI;):2BI***`HHVVQ:RLPK9M MM6;*U*8"0-&M8M%K%JB@QI*C!:B*2(T5)L,C)HM9E8RR40D)C8D-C3,M@*#4 MR:B:DM%BDVU)MBMMB2MB14C:PQ1-4E1K8T8VS#&30J@FV*VQM:T:R*Q),#-: M-JBMLIA"%,VK,4RM1BMFK"MA)(*S-3-64VV5MF:C84RRUD6QL-D4V(HK4:M& MK;6+;&-LFQBBL1L6C%!L%8K1;9DV6;(:TFJ,):J-J-MHM4:DVF:H+9-D5LR, M88E265E4EL1M5&+;%;5(FT&)*6D9-8VVC&T8C&,1:M5LH-B%M4!LC84UK2DU M%5&*6S6V-;&+1:U(9,:L4&*-5%HF+91LEM0VJ$V$FTMF9MM52JV$9HTTLK"T M-;56RF2QHABFI9EHI3*UM981J-6%,8;14MI$-BBMHK-FEL;8-;3;*5%%1*BR M4:RQLFVM)H*C4:LA6RMD2U8EBVH8P6TB6;:T8R+;-(S(IH!)`26VE+-6-$FF MQM+8R:U96:&D@LL2I1J-DL65(LHS"L8F`-;3&F9;&BU$V))J6+*5BK-EME,6 M%A$LJC&HK&-JT2H)C:M:-M$:D4:QLLFJ2J+5L46-J";,E3,FBFU,EM3,-(IB M%MK%FK-JQ6:0I6!)@L%4;8VM&V4VJ-K%I*2U9K+4%4VP4QJ8LE-F3(K9LJQ- M"6LHJ*%M-;1;1HU6QM%JV3,*%B18JU:R4DM2&DP(28DF)99:DQ93(E993606 MC-:PK89:FJRV6S8AMEDC:L:+1;6F:*HVL6K%!E%B+&T8T;4+$;0UF-9-,K&T MJ,4U8JDV36U9"(RR8K);6S36F2T9L):0EF62H*34:I;9-L:*HVH;1MIL!(F9 MLI%HVDM$,L:-1EEMK!5%)JQDM6+4;5&K(%:2BBS6ULB;40RMJ8+:$BBA;3:M MMLH5BMD"9MBDQ25&ML6S8H3%M1J6B!9MFLS9&$A4:Q;8Q&E#%8Q2S:J-3$-D M9AK46R6TVA(EIFQ"4:T%AK)1HK&U1MA96C1%JQ60TQAJJ6F;,)FP,H*T3:*+ M5%DM9L8-%2838DQM*I51M+-*&,T4E&M&TEMFK3%L++-0JQT;``._PXX^_/]M M&1.RZ"M/@B"3BG*A1/2&\O;"_.>8C+<.185'XY[">'*3(^NCU13HK0=`F#`. BT$1-2_LS,)J][[A2:#)/6IPM*H5C4(_B[DBG"A(8-\'9H``` ` end >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-09-02 16:46 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=200209021644.g82Gidu4085139@logout.sh.cvut.cz \ --to=v.haisman@sh.cvut.cz \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).