GCC 4.8.0 Status Report (2012-03-16)
The GCC 4.8 branch has been created and a first release candidate is being prepared right now. The branch is closed for now. Previous Report === http://gcc.gnu.org/ml/gcc/2013-03/msg00036.html The next report will announce the release candidate.
GCC 4.9.0 Status Report (2012-03-16), Stage 1 starts now
Status == The trunk has branched for the GCC 4.8 release and is now open again for general development, stage 1. Please consider not disrupting it too much during the RC phase of GCC 4.8 so it is possible to test important fixes for 4.8.0 on it. And more importantly, please be aware of the outage of gcc.gnu.org next week, http://gcc.gnu.org/ml/gcc/2013-03/msg00115.html ; I'd strongly recommend only starting with trunk commits after the outage is over. Quality Data Priority # Change from Last Report --- --- P11 + 1 P2 68 + 3 P3 11 - 7 --- --- Total80 - 3 Previous Report === http://gcc.gnu.org/ml/gcc/2013-03/msg00036.html The next report will be sent by Joseph.
Re: gcc 4.7.3 plans?
于 2013/1/29 星期二 19:24, Richard Biener 写道: On Tue, Jan 29, 2013 at 4:09 AM, Kenny Simpson wrote: There have been quite a few fixes on the 4.7 branch since 4.7.2 was released 4 months ago and several of the remaining regression bugs have fixes in trunk. What are the plans for 4.7.3? There will be a 4.7.3 release (shortly) before 4.8.0 releases. There is quite a number of regression fixes that are suitable for backporting to the 4.7 branch still. Richard. thanks, -Kenny The GCC 4.8 branch has been created and a first release candidate is being prepared right now. When will 4.7.3 be released? -- Best Regards, xunxun
GCC 4.8.0 Release Candidate available from gcc.gnu.org
GCC 4.8.0 Release Candidate available from gcc.gnu.org The first release candidate for GCC 4.8.0 is available from ftp://gcc.gnu.org/pub/gcc/snapshots/4.8.0-RC-20130316 and shortly its mirrors. It has been generated from SVN revision 196699. I have so far bootstrapped and tested the release candidate on x86_64-linux and i686-linux. Please test it and report any issues to bugzilla. Note that gcc.gnu.org is going to have outage next week: http://gcc.gnu.org/ml/gcc/2013-03/msg00115.html so if gcc.gnu.org is unavailable, you can grab the 4.8.0-rc1 tarballs from gcc.gnu.org mirrors, and if you need to report release blocker issues and bugzilla isn't available yet, mail me or other release managers. If all goes well, I'd like to release 4.8.0 late next week.
Re: GCC 4.9.0 Status Report (2012-03-16), Stage 1 starts now
On Sat, Mar 16, 2013 at 9:55 AM, Jakub Jelinek wrote: > Quality Data > > > Priority # Change from Last Report > --- --- > P11 + 1 > P2 68 + 3 > P3 11 - 7 > --- --- > Total80 - 3 How did you compile these numbers? The "Serious regressions" link on gcc.gnu.org results in a bug list with no P1 bugs and only 74 P2+P3 bugs. Ciao! Steven
Re: GCC 4.9.0 Status Report (2012-03-16), Stage 1 starts now
On 2013.03.16 at 14:51 +0100, Steven Bosscher wrote: > On Sat, Mar 16, 2013 at 9:55 AM, Jakub Jelinek wrote: > > Quality Data > > > > > > Priority # Change from Last Report > > --- --- > > P11 + 1 > > P2 68 + 3 > > P3 11 - 7 > > --- --- > > Total80 - 3 > > How did you compile these numbers? The "Serious regressions" link on > gcc.gnu.org results in a bug list with no P1 bugs and only 74 P2+P3 > bugs. Works for me: http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=4.9&target_milestone=4.6.4&target_milestone=4.7.3&target_milestone=4.8.0&target_milestone=4.9.0&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&gcchost_type=allwordssubstr&gcchost=&gcctarget_type=allwordssubstr&gcctarget=&gccbuild_type=allwordssubstr&gccbuild=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= 80 bugs found. ID▲ Sev Pri▲Assignee▲ Status▲ Resolution Summary 54114 nor P1 unassigned NEW --- [4.8/4.9 Regression] variable-tracking performance regression from 4.8-20120610 to 4.8-20120701 49234 min P2 aldyh NEW --- [4.6/4.7/4.8/4.9 Regression] -Wstrict-overflow gives obviously unwarranted warning ... -- Markus
Re: GCC 4.9.0 Status Report (2012-03-16), Stage 1 starts now
On Sat, Mar 16, 2013 at 02:51:03PM +0100, Steven Bosscher wrote: > On Sat, Mar 16, 2013 at 9:55 AM, Jakub Jelinek wrote: > > Quality Data > > > > > > Priority # Change from Last Report > > --- --- > > P11 + 1 > > P2 68 + 3 > > P3 11 - 7 > > --- --- > > Total80 - 3 > > How did you compile these numbers? The "Serious regressions" link on > gcc.gnu.org results in a bug list with no P1 bugs and only 74 P2+P3 > bugs. That is the 4.9 list, not 4.8 list. Jakub
Re: GCC 4.9.0 Status Report (2012-03-16), Stage 1 starts now
On Sat, Mar 16, 2013 at 3:04 PM, Jakub Jelinek wrote: > On Sat, Mar 16, 2013 at 02:51:03PM +0100, Steven Bosscher wrote: >> On Sat, Mar 16, 2013 at 9:55 AM, Jakub Jelinek wrote: >> > Quality Data >> > >> > >> > Priority # Change from Last Report >> > --- --- >> > P11 + 1 >> > P2 68 + 3 >> > P3 11 - 7 >> > --- --- >> > Total80 - 3 >> >> How did you compile these numbers? The "Serious regressions" link on >> gcc.gnu.org results in a bug list with no P1 bugs and only 74 P2+P3 >> bugs. > > That is the 4.9 list, not 4.8 list. Then the link on the homepage needs updating. It now has: http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=4.8&target_milestone=4.6.4&target_milestone=4.7.3&target_milestone=4.8.0&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&bugidtype=include&list_id=57595 Ciao! Steven
Re: GCC 4.9.0 Status Report (2012-03-16), Stage 1 starts now
On Sat, Mar 16, 2013 at 03:08:51PM +0100, Steven Bosscher wrote: > > That is the 4.9 list, not 4.8 list. > > Then the link on the homepage needs updating. > > It now has: > http://gcc.gnu.org/bugzilla/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=4.8&target_milestone=4.6.4&target_milestone=4.7.3&target_milestone=4.8.0&known_to_fail_type=allwordssubstr&known_to_work_type=allwordssubstr&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&priority=P1&priority=P2&priority=P3&bugidtype=include&list_id=57595 The link is correct there, either you need to reload the home page, or you've cliked on the 4.8 link, not 4.9 link. Jakub
Comparing compile times and binary size for GCC compiling a few GCC releases
Hello, Below are some compile times and sizes I measured for a bunch of GCC releases. The test compilers are listed in the tables. All of them were compiled with gcc 4.7.2 (i.e. not bootstrapped). Test machine is gcc110 (powerpc64) which was otherwise idle. Times are "user" times in seconds, from /usr/bin/time. GCC 4.4 is not included because it failed to build with default configure options (linker error, "undefined reference to symbol 'ppl_finalize'"). Interesting observations: * GCC 4.8.0 is not slower than, say, GCC 4.2.4 for an optimized non-debug build. * with debug info, compilation time has increased by ~17% (but debug info is much more accurate than before) * cc1 for GCC 4.8.0 cc1 is 2 times the size of cc1 for GCC 4.2.4! * cc1 for GCC 4.8.0 has a much larger .bss section than previous releases I started looking into this because I've noticed compilations of many small files being slower. I wonder if the larger cc1 and .bss sections could be in part responsible for that...? Ciao! Steven Test set are cc1-i files for trunk r189478, configured with release checking: Compiler flags: -S -O2 -fpreprocessed: Run 1 Run 2 Run 3 Avg Diff 4.2.4 368.72 368.72 368.85 369 0.0% 4.3.6 337.28 336.01 336.18 336 -8.9% 4.5.4 335.73 337.86 339.75 338 -8.4% 4.6.3 343.95 345.86 341.11 344 -6.8% 4.7.2 370.06 369.66 376.77 372 0.8% 4.8.0 374.84 373.59 374.13 374 1.4% Compiler flags: -S -O2 -g -fpreprocessed: Run 1 Run 2 Run 3 Avg Diff 4.2.4 391.47 390.43 393.22 392 0.0% 4.3.6 356.55 357.02 358.14 357 -8.9% 4.5.4 389.00 389.50 396.37 392 0.0% 4.6.3 418.18 420.67 426.80 422 7.7% 4.7.2 444.98 445.67 452.52 448 14.3% 4.8.0 456.81 456.96 468.29 461 17.6% cc1 binary size: textdatabss dec hex filename 6460157 374800 535656 7370613 707775 4.2.4/cc1 7558042 666080 436744 8660866 842782 4.3.6/cc1 10917491775144 684544 12377179bcdc5b 4.5.4/cc1 11715323489512 984224 13189059c93fc3 4.6.3/cc1 12351879484968 1193672 14030519d616b7 4.7.2/cc1 13731087499080 781496 15011663e50f4f 4.8.0/cc1 Top 10 files: 4.2.4 (327 .o files): textdata bss dec hex filename 1021761504 212 103892 195d4 combine.o 11009677281429 119253 1d1d5 builtins.o 1243682304 28 126700 1eeec fold-const.o 12972431122804 135640 211d8 c-common.o 1427196032 992 149743 248ef dwarf2out.o 173416 216 0 173632 2a640 insn-attrtab.o 195168 18144 448 213760 34300 rs6000.o 206575 14848 0 221423 360ef insn-emit.o 3059321368 0 307300 4b064 insn-recog.o 742464 264 16 742744 b5558 insn-automata.o 7000225 459384 473148 7932757 790b55 (TOTALS) 4.3.6 (354 .o files): textdata bss dec hex filename 1049361616 204 106756 1a104 combine.o 13404088401429 144309 233b5 builtins.o 1428972512 28 145437 2381d fold-const.o 14585034642992 152306 252f2 c-common.o 15363164241032 161087 2753f dwarf2out.o 215076 19232 480 234788 39524 rs6000.o 228427 16416 0 244843 3bc6b insn-emit.o 247248 240 0 247488 3c6c0 insn-attrtab.o 3163001288 0 317588 4d894 insn-recog.o 803520 296 16 803832 c43f8 insn-automata.o 7941854 750682 348048 9040584 89f2c8 (TOTALS) 4.5.4 (393 .o files): textdata bss dec hex filename 1150293081 160 118270 1cdfe c-decl.o 1565649376 975 166915 28c03 builtins.o 17665039963080 183726 2cdae c-common.o 1966832720 28 199431 30b07 fold-const.o 22473586651200 234600 39468 dwarf2out.o 263028 235603080 289668 46b84 rs6000.o 311123 22944 0 334067 518f3 insn-emit.o 383160 264 0 383424 5d9c0 insn-attrtab.o 3929321592 0 394524 6051c insn-recog.o 1714644 320 16 1714980 1a2b24 insn-automata.o 10907556 880995 436874 12225425 ba8b91 (TOTALS) 4.6.3 (409 .o files): textdata bss dec hex filename 1577009352 63 167115 28ccb builtins.o 164455 224 0 164679 28347 gcc-options.o 195747 328 0 196075 2fdeb options.o 1981572432 28 200617 30fa9 fold-const.o 24908790171200 259304 3f4e8 dwarf2out.o 281748 240603152 308960 4b6e0 rs6000.o 373251 23600 0 396851 60e33 insn-emit.o 3959961464 0 397460 61094 insn-recog.o 6416241624 0 643248 9d0b0 insn-attrtab.o 1729733 344 16 1730093 1a662d insn-automata.o 11917280 545628 280335 12743243 c2724b (TOTALS) 4.
Re: Comparing compile times and binary size for GCC compiling a few GCC releases
Hi, On Sat, 2013-03-16 at 19:44 +0100, Steven Bosscher wrote: > * cc1 for GCC 4.8.0 has a much larger .bss section than previous releases But according to the table that followed ... > cc1 binary size: > textdatabss dec hex filename > 6460157 374800 535656 7370613 707775 4.2.4/cc1 > 7558042 666080 436744 8660866 842782 4.3.6/cc1 > 10917491775144 684544 12377179bcdc5b 4.5.4/cc1 > 11715323489512 984224 13189059c93fc3 4.6.3/cc1 > 12351879484968 1193672 14030519d616b7 4.7.2/cc1 > 13731087499080 781496 15011663e50f4f 4.8.0/cc1 ... 4.7 .bss is 1193672 and 4.8 .bss is 781496 Am I missing something? > > I started looking into this because I've noticed compilations of many > small files being slower. I wonder if the larger cc1 and .bss sections > could be in part responsible for that...? Could probably be. Compiling many small files puts pressure on compiler executable startup and larger executables result in slower startup times (well maybe not always immediately, but eventually -- at some point in time code/data will have to be paged in or initialized.. ), doesn't it? I'm curious, do you happen to have some numbers for those 'small file' cases? Cheers, Oleg
gcc-4.7-20130316 is now available
Snapshot gcc-4.7-20130316 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20130316/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.7 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_7-branch revision 196717 You'll find: gcc-4.7-20130316.tar.bz2 Complete GCC MD5=8a3dff9476d93dfa17d2f0cdb7a0f9ce SHA1=8a879f0d77991ebae2534792fc6e51836fcd3f53 Diffs from 4.7-20130309 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.7 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
