Git mirror needs a run of "git gc"
Right now, each fresh clone needs to create a compressed pack, which takes quite a while. (I think, there might be something else wrong with the repository.)
gcc-4.3-20100131 is now available
Snapshot gcc-4.3-20100131 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.3-20100131/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.3 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-4_3-branch revision 156418 You'll find: gcc-4.3-20100131.tar.bz2 Complete GCC (includes all of below) gcc-core-4.3-20100131.tar.bz2 C front end and core compiler gcc-ada-4.3-20100131.tar.bz2 Ada front end and runtime gcc-fortran-4.3-20100131.tar.bz2 Fortran front end and runtime gcc-g++-4.3-20100131.tar.bz2 C++ front end and runtime gcc-java-4.3-20100131.tar.bz2 Java front end and runtime gcc-objc-4.3-20100131.tar.bz2 Objective-C front end and runtime gcc-testsuite-4.3-20100131.tar.bz2The GCC testsuite Diffs from 4.3-20100124 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.3 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.
Support for export keyword to use with C++ templates ?
On Sat, Jan 30, 2010 at 4:23 AM, Michael Witten [...] > However, I have a gut feeling that at least a restricted version of > 'export' (or a cousin of 'export') could be both useful and trivial to > implement: [...] > Those were my thoughts too. Since such a change must happen in small steps, I would be interested to know how 'acceptable' would a limited implementation be at first ? Like the command line options I have seen declared 'experimental' in the gcc manual before ... The idea of a "cousin of" or "variation of" is less important though, as I am interested in standard conformance, even if partly implemented. Timothy Madden
Re: Support for export keyword to use with C++ templates ?
On Sat, Jan 30, 2010 at 4:05 AM, Paolo Carlini wrote: [...] > Even for implementors knowing *very* well both the details of the C++ > standard and the internals of a specific front-end, implementing export > is an *highly* non-trivial task. [...] Yes, everyone is telling me that, but could someone please describe a little what would be the first problems that would have to be addressed for export with the current g++ implementation ? Or summarise the steps that would have to be taken for a first attempt at export ? Did someone here said they tried some things before ? Thank you, Timothy Madden
Re: Support for export keyword to use with C++ templates ?
On 02/01/2010 01:26 AM, Timothy Madden wrote: > Since such a change must happen in small steps, I would be interested > to know how 'acceptable' would a limited implementation be at first ? > Like the command line options I have seen declared 'experimental' in > the gcc manual before ... > As I see the issue, you should first check over the next months that the feature is not deprecated by ISO. Then start learning about the internals of GCC and eventually propose a detailed plan explaining how you want to attack the problem, because before that it's extremely unlikely that the C++ front-end maintainers could even consider reviewing patches from a novice for such an hard to implement feature. That said, if you *really* plan contributing to GCC, maybe outside export first (which seems a terribly good idea to me) first and foremost, read the relevant web page: http://gcc.gnu.org/contribute.html and start immediately the paperwork for the Copyright assignment, because it takes time. Paolo.
Re: Support for export keyword to use with C++ templates ?
Timothy Madden writes: > On Sat, Jan 30, 2010 at 4:05 AM, Paolo Carlini > wrote: > [...] >> Even for implementors knowing *very* well both the details of the C++ >> standard and the internals of a specific front-end, implementing export >> is an *highly* non-trivial task. [...] > > Yes, everyone is telling me that, but could someone please describe a > little what would be the first problems that would have to be > addressed for export with the current g++ implementation ? Or > summarise the steps that would have to be taken for a first attempt at > export ? Aside from what Paolo said, the first requirement is clearly going to be the ability to write out and read in the frontend IR. Ian
