Re: dejagnu version update?

2020-05-13 Thread Christophe Lyon
On Wed, 13 May 2020 at 19:44, Jonathan Wakely via Gcc wrote: > > On Wed, 13 May 2020 at 18:19, Mike Stump via Gcc wrote: > > > > I've changed the subject to match the 2015, 2017 and 2018 email threads. > > > > On May 13, 2020, at 3:26 AM, Thomas Schwinge > > wrote: > > > > > > Comparing DejaGnu

Re: dejagnu version update?

2020-05-13 Thread Maciej W. Rozycki
On Wed, 13 May 2020, Rainer Orth wrote: > > I'm in favour of requiring 1.5.3 or later, so 1.6 would be OK for me. > > If we go beyond 1.5.x, we need to go all the way up to 1.6.2: 1.6 and > 1.6.1 have an ugly bug that can miss timeouts, causing tests to hang > indefinitely until one manually kill

Re: dejagnu version update?

2020-05-13 Thread Jonathan Wakely
On Wed, 13 May 2020 at 18:19, Mike Stump via Gcc wrote: > > I've changed the subject to match the 2015, 2017 and 2018 email threads. > > On May 13, 2020, at 3:26 AM, Thomas Schwinge wrote: > > > > Comparing DejaGnu/GCC testsuite '*.sum' files between two systems ("old" > > vs. "new") that ought t

Re: dejagnu version update?

2020-05-13 Thread Rainer Orth
Jonathan Wakely via Gcc writes: >> I had previously approved the update to 1.5.3, but no one really wanted >> it as no one updated the requirement. Let's have the 1.6 discussion. >> I'm not only inclined to up to 1.6, but to actually edit it in this time. > > Would the tests actually refuse to r

Re: dejagnu version update?

2020-05-13 Thread Rob Savoye
On 5/13/20 10:51 AM, Mike Stump wrote: > So, now that ubuntu 20.04 is out and RHEL 8 is out, and they both > contain 6, and SLES has 6 and since we've been sitting at 1.4.4 for > so long, anyone want to not update dejagnu to require 1.6? We do still find and fix bugs occasionally. :-) And 1.4.4

dejagnu version update?

2020-05-13 Thread Mike Stump
I've changed the subject to match the 2015, 2017 and 2018 email threads. On May 13, 2020, at 3:26 AM, Thomas Schwinge wrote: > > Comparing DejaGnu/GCC testsuite '*.sum' files between two systems ("old" > vs. "new") that ought to return identical results, I found that they > didn't: > I have not

DejaGnu/GCC testsuite behavior regarding multiple 'dg-do'

2020-05-13 Thread Thomas Schwinge
Hi! Comparing DejaGnu/GCC testsuite '*.sum' files between two systems ("old" vs. "new") that ought to return identical results, I found that they didn't: @@ -75032,6 +75023,7 @@ PASS: g++.dg/expr/bitfield4.C -std=c++98 (test for excess errors) PASS: g++.dg/expr/bitfield5.C -std=c++14