gcc-4.6-20130319 is now available
Snapshot gcc-4.6-20130319 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20130319/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_6-branch revision 196788 You'll find: gcc-4.6-20130319.tar.bz2 Complete GCC MD5=265bd55b0dc0cd5a5d59a352eb8c724b SHA1=837283364781630090d8aca9d0a96fffa6bbaa9b Diffs from 4.6-20130315 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.6 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.
gcc-4.8-20130319 is now available
Snapshot gcc-4.8-20130319 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.8-20130319/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.8 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_8-branch revision 196788 You'll find: gcc-4.8-20130319.tar.bz2 Complete GCC MD5=cd15d394c86d2afdb3d4d989bc46609a SHA1=7a0bf9f0a5e8cffe5b9b6f08d2a89ed2141f7ced Diffs from 4.8-20130310 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.8 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.
gcc-4.9-20130319 is now available
Snapshot gcc-4.9-20130319 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.9-20130319/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.9 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 196788 You'll find: gcc-4.9-20130319.tar.bz2 Complete GCC MD5=b83d87d9c3c586fc2e284a7d8f73b22f SHA1=9b161e0eaec6b1051d7415cc449d349b0180607f Diffs from 4.9-20130317 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.9 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.
gcc-4.7-20130319 is now available
Snapshot gcc-4.7-20130319 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20130319/ 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 196788 You'll find: gcc-4.7-20130319.tar.bz2 Complete GCC MD5=4d3bf47fc961926d802cfe779f5a8682 SHA1=5ca275eda7fd0622a2b4b4a3db8561080e858123 Diffs from 4.7-20130316 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.
Re: anonymous namespaces in GCC source code
On 18/03/13 18:50, Lawrence Crowl wrote: On 3/18/13, Gabriel Dos Reis wrote: I have been having discussion with Andrew about uses of anonymous namespaces in GCC source code. I seem to remember that they used to cause troubles when doing binary diff during bootsrap because we use random names to ensure uniqueness of names; but are we still doing that? We could have an option to take the compile time (and probably some parts of the file path) out of the random number generator. Why not hash the file name and line-number or something? Or add true anonymous name spaces? Why do they require some sort of name? Alec
Приветульки
В спорте часто происходят «договорные матчи». Результат игры определен заранее заинтересованными лицами: тренерами, владельцами клубов и участниками команд. Игрок всегда просчитает долю вероятности, но все-таки это не может быть гарантией, что он вернет деньги и получит сверхприбыль. У нас есть информация о победителях. Знание результатов - залог успеха. Skype:dogmath99 E-mail: abovs...@yahoo.com ICQ:687378136
Proposal: New Layer Maybe
Hey all I've been quietly spending the last years working on my python-front-end in the background. And over the last few years always been thinking that gcc could be simpler for front-end-developers. I am just going to post up this simple high-level proposal just to gauge the opinion of the gods that are GCC developers as i don't really want to start working on something in a certain way in vain. 1 - How about an _optional_ library for front-ends, and some generators: The library say libgcchelper could be optionally used in the front-end code so developers could have a simpler higher-level api (something akin to Kaleidoscope from llvm http://llvm.org/docs/tutorial/LangImpl3.html) to generate code ready for GCC. So over all it will be a high level IL which gets lowered to GENERIC then we call gcc middle-end as normal. It could also provide some generators to build a config.lang/lang.specs and your compiler driver and the necessary boiler-plate code like langhooks. This could work well so existing front-ends can use their code as usual and new front-ends could use the generates to get the boiler plate code done for them and then able to use GENERIC if they wish. But comes with the cost of extra code to maintain which probably won't get picked up. in the existing front-ends. --- 2- Another way to go is, implementing these generators and also adding more code to the existing GENERIC api to make things simpler and maybe some more error handling to GENERIC. By make things simpler i would mean making new constructs like: Function *F = Function::Create(FT, Function::ExternalLinkage, Name, TheModule); ... BasicBlock *BB = BasicBlock::Create(getGlobalContext(), "entry", TheFunction); Instead of the mountain of different ways you can make functions at the moment. I think what makes GENERIC is so confusing is BIND_EXPR's to implement blocks of code. As well as SUB/SUPER context's etc. Feels very abstract talking about code in this way without knowing the internals very well. Having a builder class like llvm to handle a lot of the complicated fiddly trickery pokery to get things working. But this is difficult because the tree api code is pretty much black magic to me most of the time. But in the end probably the ideal solution. I think with the move to c++ is probably going to get much simpler with time. --- This probably looks more like a brain dump but i think i want to work on making something better in gcc and i think i can do something here some opinions or discussion would be cool. --Phil
Fwd: GSoC Proposal
Dear GCC, I have been told that the Project - "Implement regular expressions in c++" mentored by Sir Benjamin De Kosnik is not completed and is available for this year GSoC project also by the the Mentor. Since my course of study for this semester is Generic Programming using C++ and i am working on that project for last one and half months are so i would like to complete that project if the you give me a chance... waiting for your reply.. thank you.. -- Saikiran A 6th Semester, Computer Science and Engineering, P.E.S. Institute of Technology, Bangalore.
