On 05/08/2015 10:40 AM, Thomas Schwinge wrote:
> Hi!
>
> On Thu, 7 May 2015 13:39:40 +0200, Jakub Jelinek wrote:
>> On Thu, May 07, 2015 at 01:26:57PM +0200, Rainer Orth wrote:
>>> As reported in the PR, with the addition of all those OpenACC tests,
>>> libgomp make check times have skyrocketed
Hi!
On Thu, 7 May 2015 13:39:40 +0200, Jakub Jelinek ja...@redhat.com wrote:
On Thu, May 07, 2015 at 01:26:57PM +0200, Rainer Orth wrote:
As reported in the PR, with the addition of all those OpenACC tests,
libgomp make check times have skyrocketed since the testsuite is still
run
On May 7, 2015, at 4:39 AM, Jakub Jelinek ja...@redhat.com wrote:
On Thu, May 07, 2015 at 01:26:57PM +0200, Rainer Orth wrote:
As reported in the PR, with the addition of all those OpenACC tests,
libgomp make check times have skyrocketed since the testsuite is still
run sequentially.
Even
On Thu, May 07, 2015 at 01:26:57PM +0200, Rainer Orth wrote:
As reported in the PR, with the addition of all those OpenACC tests,
libgomp make check times have skyrocketed since the testsuite is still
run sequentially.
Even on a reasonably fast x86 machine (4 x 2.0 Ghz Xeon E7450) the run
As reported in the PR, with the addition of all those OpenACC tests,
libgomp make check times have skyrocketed since the testsuite is still
run sequentially.
Even on a reasonably fast x86 machine (4 x 2.0 Ghz Xeon E7450) the run
takes 4286 seconds.
On slower sparc boxes (1.2 GHz UltraSPARC-T2)
