Re: Which Binutils should I use for performing daily regression test on trunk?

2011-12-22 Thread Hans-Peter Nilsson
> From: Terry Guo > Date: Wed, 21 Dec 2011 04:25:46 +0100 > I plan to set up daily regression test on trunk for target > ARM-NONE-EABI and post results to gcc-testresults mailing > list. Nice. I see others do it for that target, but apparently not for a pristine tree (the results having many fa

Re: Which Binutils should I use for performing daily regression test on trunk?

2011-12-22 Thread Ye Joey
On Thu, Dec 22, 2011 at 12:43 AM, Ian Lance Taylor wrote: > Terry Guo writes: > >> I plan to set up daily regression test on trunk for target >> ARM-NONE-EABI and post results to gcc-testresults mailing list. Which >> Binutils should I use, the Binutils trunk or the latest released >> Binutils? A

gcc-4.5-20111222 is now available

2011-12-22 Thread gccadmin
Snapshot gcc-4.5-20111222 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.5-20111222/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.5 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/branches

Re: GCC 4.7.0 Status Report (2011-12-06)

2011-12-22 Thread Joseph S. Myers
On Thu, 22 Dec 2011, Gary Funck wrote: > On 12/06/11 01:18:28, Joseph S. Myers wrote: > > [...] It still seems reasonable to aim for > > entering Stage 4 (regression fixes and documentation changes only) in > > early January and the 4.7.0 release in March or April. > > At what point in time would

Re: GCC 4.7.0 Status Report (2011-12-06)

2011-12-22 Thread Gary Funck
On 12/06/11 01:18:28, Joseph S. Myers wrote: > [...] It still seems reasonable to aim for > entering Stage 4 (regression fixes and documentation changes only) in > early January and the 4.7.0 release in March or April. At what point in time would the GCC 4.7 branch be created, and the trunk would

Re: A case exposing code sink issue

2011-12-22 Thread Richard Guenther
On Thu, Dec 22, 2011 at 9:25 AM, Jiangning Liu wrote: >> Yes, the number of iterations of the i loop simply is too difficult fo >> our loop iteration calculator to comprehend: >> >>   for (i=k; i<500; i+=k) >> >> iterates for roundup((500-k)/k) time.  In particular if the step is >> non-constant o

RE: A case exposing code sink issue

2011-12-22 Thread Jiangning Liu
> Yes, the number of iterations of the i loop simply is too difficult for > our loop iteration calculator to comprehend: > > for (i=k; i<500; i+=k) > > iterates for roundup((500-k)/k) time. In particular if the step is > non-constant our nr-of-iteration calculator gives up. > I'm trying to g