On 10/04/13 04:51, Geert Bosch wrote:
>
> On Apr 9, 2013, at 22:19, Segher Boessenkool
> wrote:
>
>> Some numbers, 16-core 64-thread POWER7, c,c++,fortran bootstrap:
>> -j6: real57m32.245s
>> -j60: real38m18.583s
>
> Yes, these confirm mine. It doesn't make sense to look at more
> par
On Wed, Apr 10, 2013 at 4:51 AM, Geert Bosch wrote:
>
> On Apr 9, 2013, at 22:19, Segher Boessenkool
> wrote:
>
>> Some numbers, 16-core 64-thread POWER7, c,c++,fortran bootstrap:
>> -j6: real57m32.245s
>> -j60: real38m18.583s
>
> Yes, these confirm mine. It doesn't make sense to look a
Hi,
I have this problem in private backend, but it is reproducible on
x86-gcc also, so I suppose core GCC probems. Lets consider simple
example:
unsigned int buffer[10];
__attribute__((noinline)) void
myFunc(unsigned int a, unsigned int b, unsigned int c)
{
unsigned int tmp;
if( a & 0x2 )
On Wed, Apr 10, 2013 at 11:46 AM, Konstantin Vladimirov
wrote:
> Hi,
>
> I have this problem in private backend, but it is reproducible on
> x86-gcc also, so I suppose core GCC probems. Lets consider simple
> example:
>
> unsigned int buffer[10];
>
> __attribute__((noinline)) void
> myFunc(unsigne
Quoting David Brown :
I presume fixing the slow, inefficient serial nature of autotools is a
hard job - otherwise it would have been done already. But any
improvements there could have big potential benefits.
I think it's more likely because it is tedious and time-consuming to do,
and is not
On Tue, Apr 9, 2013 at 9:50 PM, David Brown wrote:
> And of course if someone figures out how to speed up ./configure with
> gcc, the same technique could probably be used on thousands of other
> programs.
Is gcc already using a new enough autoconf (2.64+) to take advantage
of shell functions? T
On 4/10/2013 2:52 AM, Richard Biener wrote:
On Wed, Apr 10, 2013 at 4:51 AM, Geert Bosch wrote:
On Apr 9, 2013, at 22:19, Segher Boessenkool wrote:
Some numbers, 16-core 64-thread POWER7, c,c++,fortran bootstrap:
-j6: real57m32.245s
-j60: real38m18.583s
Yes, these confirm mine. It
Hi
For those interested in participating in the Google Summer of
Code, the Google Open Source Program Office is holding a video
conference using Google Hangouts tomorrow which should
be archived on YouTube afterwards.
https://plus.google.com/events/cpooa4srhdkp7o6ttsu88tcuhl4
This is a good opp
> "Joern" == Joern Rennecke writes:
Joern> The likelyhood that a test depends on the outcome of the last few
Joern> n tests is rather low. So you could tests speculatively with an
Joern> incomplete set of defines, and then re-run them when you have
Joern> gathered all the results from the pr
