On Mon, Jan 3, 2011 at 12:29 AM, Eric Botcazou ebotca...@adacore.com wrote:
I was wondering about that lately. Should testsuite failures with
--enable-checking=all be reported? IIRC, the 4.5 branch won't even
bootstrap with that setting.
I'd think so, but only for the trunk probably.
And
On 3 January 2011 08:05, Eric Botcazou ebotca...@adacore.com wrote:
Any idea why these results would be so poor ?
Because of your bootstrap settings, more precisely --enable-checking=all.
I was wondering about that lately. Should testsuite failures with
--enable-checking=all be reported? IIRC,
I was wondering about that lately. Should testsuite failures with
--enable-checking=all be reported? IIRC, the 4.5 branch won't even
bootstrap with that setting.
I'd think so, but only for the trunk probably.
--
Eric Botcazou
For reasons unknown I ran the testsuite for well over three days before
finally giving up. This is a quad core Intel i7 with 8G of meemory and the
bootstrap took forever and the testsuite .. well the results below speak
for themselves.
Any idea why these results would be so poor ?
zaphod $ gas
On Sun, Jan 2, 2011 at 7:04 PM, Dennis Clarke dcla...@blastwave.org wrote:
For reasons unknown I ran the testsuite for well over three days before
finally giving up. This is a quad core Intel i7 with 8G of meemory and the
bootstrap took forever and the testsuite .. well the results below speak
Any idea why these results would be so poor ?
Because of your bootstrap settings, more precisely --enable-checking=all.
--
Eric Botcazou
