gcc-4.7-20110514 is now available
Snapshot gcc-4.7-20110514 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20110514/ 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/trunk revision 173763 You'll find: gcc-4.7-20110514.tar.bz2 Complete GCC (includes all of below) MD5=d30c081133c985eae9f4e96804062462 SHA1=55cb7991c44afe2ff19866576c469a8cfd1a6616 gcc-core-4.7-20110514.tar.bz2C front end and core compiler MD5=1bcd89179518e7e84af90fd91b1c4d30 SHA1=6e4516954dbaef15779b87a3573c7ee377122c33 gcc-ada-4.7-20110514.tar.bz2 Ada front end and runtime MD5=af64f121c91c66758fec5f9762f20a2a SHA1=5f3e8364ad168d7047e41992ee080f104ffbed2e gcc-fortran-4.7-20110514.tar.bz2 Fortran front end and runtime MD5=d489295d4f29123ed46c028e3a5b57f2 SHA1=0a638546f06af32b0095c24724a2d2a2395a0274 gcc-g++-4.7-20110514.tar.bz2 C++ front end and runtime MD5=442fccbdb65af53491ac51d147aa0d65 SHA1=e2c4687ed396df3535fa0464657f06b9403edbe3 gcc-go-4.7-20110514.tar.bz2 Go front end and runtime MD5=43fc858311764ce2d0a076ab114dffb0 SHA1=f2b0f7bb7d347a7a04f67129ac1376021de1ea46 gcc-java-4.7-20110514.tar.bz2Java front end and runtime MD5=847bb6485dd045175ebf4499338ea865 SHA1=5512213b76425481538152fa17f355ce2da561a0 gcc-objc-4.7-20110514.tar.bz2Objective-C front end and runtime MD5=2473d901db11a25d151c2fc9a297cc08 SHA1=131192b8313bfb445aba4e76c3c72d445b47873d gcc-testsuite-4.7-20110514.tar.bz2 The GCC testsuite MD5=08432aefaf79fa8d12811aa02bad96bb SHA1=63a13d3a151ba2a796bafc2b827bf9f7ba110186 Diffs from 4.7-20110507 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.
Differences in optimisations on different versions of same program
Hi I have been looking at the intermediate representation (IR) dumped by gcc (4.4.5, cross compiled for powerpc) through the switch -fdump-tree-all. An experiment I carried out was to manually make the IR compilable, i.e. write a C program with the same control flow (using "if" and "goto") and variable usage as in the IR. I compiled this program and found that the binary was quite different from the one generated by compiling the original program. In the former case the "for" loop gets unrolled whereas in the latter it doesn't. Can some one please advise why they are different? I am attaching the relevant files (zipped archive). test1.c - Original program test1_IR.c - The compilable form of the IR. test1.c.126t.final_cleanup - What I believe is the final step of the front end optimisations carried out by gcc (this was one of the files output using -fdump-tree-all) test1_objdump - Object dump of executable generated from test1.c test1_IR_opt_objdump - Object dump of executable generated from test1_IR.c Command used to dump IR: powerpc-elf-gcc -pedantic -Wcomment -fno-asm -fsigned-char -W -Wparentheses -Wreturn-type -Wswitch -Wunused -Wsign-compare -Wimplicit -Wreturn-type -Wshadow -Wpointer-arith -Wwrite-strings -Wsign-compare -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -O2 -fdump-tree-all -msim -msoft-float -o test1.elf test1.c Command used to compile test1_IR.c: same options as above but without -fdump-tree-all and adding -g to generate debugging info for gdb. http://old.nabble.com/file/p31620771/source_files.zip source_files.zip -- View this message in context: http://old.nabble.com/Differences-in-optimisations-on-different-versions-of-same-program-tp31620771p31620771.html Sent from the gcc - Dev mailing list archive at Nabble.com.
