building gcc-4.3.5 for sh-elf --with-newlib --enable-language="c,c++"
Hi all I have build the toolchain: binutils-2.20 gcc-4.3.5 newlib-1.18.0 for target sh-elf for c and c++ successfully T htink it will be usefull to write this (very very usefull for firmware developer) news onto the successfully building list How can I do this? Do I need to make alse the test suite? Let me know or write me where to leanr more about Best regards -- Ing. Fabio Giovagnini Aurion s.r.l. P.I e C.F. 00885711200 skype: aurion.giovagnini Tel. +39.051.594.78.24 Cell. +39.335.83.50.919 www.aurion-tech.com
GCC 4.4.5 Status Report (2010-10-01)
Status == GCC 4.4.5 release tarballs have been uploaded to gcc.gnu.org and to ftp.gnu.org, the 4.4 branch is again open for commits under the usual release branch rules. It took a little longer than I've initially expected, but there were important P1 regressions that caused delays. I'll announce the release once mirrors had some time to download it. GCC 4.4.6 is planned roughly for the end of January, unless some severe issue forces us to release it earlier. Quality Data Priority # Change from Last Report --- --- P10 0 P2 102 +17 P3 15 - 1 --- --- Total 117 +16 Previous Report === http://gcc.gnu.org/ml/gcc/2010-04/msg01018.html The next report for 4.4.5 will be sent by myself again.
Re: Range-based for in c++98
On 09/20/2010 07:06 PM, Rodrigo Rivas wrote: Are you sure? As I said in other post, I am no longer sure that the C++0x draft forbids the type definition in this context. But I'm no expert in standarese, so I'm still undecided. It took me some searching, but yes, it does: "A type-specifier-seq shall not define a class or enumeration unless it appears in the type-id of an alias-declaration (7.1.3)." Normal declarations don't have a type-specifier-seq, they have a decl-specifier-seq. I would change cp_parser_range_for to use cp_parser_decl_specifier_seq instead of cp_parser_type_specifier_seq and then wait to complain about defining a type until after we've seen the ':'. Jason
gcc-testresults submissions
Hi, I was wondering how people manage to get the branch and svn revision into the subject of a contrib/test_summary submission. Is it supposed to be detected automagically? Or is it something you add with configure --with-pkgversion when building? Thanks in advance, Sean
Re: gcc-testresults submissions
On 10/01/2010 10:58 AM, Sean McGovern wrote: > Hi, > > I was wondering how people manage to get the branch and svn revision into the > subject of a contrib/test_summary submission. Is it supposed to be detected > automagically? Or is it something you add with configure --with-pkgversion > when building? ./contrib/gcc_update creates the file involved, as i recall. r~
Re: gcc-testresults submissions
"Sean McGovern" writes: > I was wondering how people manage to get the branch and svn revision into the > subject of a contrib/test_summary submission. Is it supposed to be detected > automagically? Or is it something you add with configure --with-pkgversion > when building? It is recorded by contrib/gcc_update and then picked up by gcc/configure. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
Re: gcc-testresults submissions
Thanks. I guess I missed that part in the online documentation. -- Sean --Original Message-- From: Richard Henderson To: Sean McGovern Cc: gcc@gcc.gnu.org Subject: Re: gcc-testresults submissions Sent: Oct 1, 2010 14:02 On 10/01/2010 10:58 AM, Sean McGovern wrote: > Hi, > > I was wondering how people manage to get the branch and svn revision into the > subject of a contrib/test_summary submission. Is it supposed to be detected > automagically? Or is it something you add with configure --with-pkgversion > when building? ../contrib/gcc_update creates the file involved, as i recall. r~
