From: Rob Savoye <rob@welcomehome.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
"Maciej W. Rozycki" <macro@wdc.com>
Cc: Jonathan Wakely via Gcc <gcc@gcc.gnu.org>,
Mike Stump <mikestump@comcast.net>,
Thomas Schwinge <thomas@codesourcery.com>,
dejagnu@gnu.org
Subject: Re: dejagnu version update?
Date: Thu, 14 May 2020 09:12:11 -0600 [thread overview]
Message-ID: <274e2a71-ddb0-18cc-70c1-4ca9ccf8bd29@welcomehome.org> (raw)
In-Reply-To: <yddtv0izk0d.fsf@CeBiTec.Uni-Bielefeld.DE>
On 5/14/20 8:08 AM, Rainer Orth wrote:
>> stops responding for whatever reason. I have come up with a solution
>> (that I'd be happy to upstream, except that DejaGNU maintenance seems to
>> have been dead for like a year now), which I have also confirmed to be
>> required with current DejaGNU Git master so it must be a different one,
>> and I would like to know how it might be related to the bug you mention.
I feel I need to bring up the issue that DejaGnu is 30 years old, and
it's two maintainers are either trying to pay bills, or trying to
retire, or both... This problem will effect more projects in the future,
not just DejaGnu. I'd love to see if anyone would like to become a
co-maintainer, who preferably will be actively working for a few decades
still. I think most people on these lists make their income from working
on the toolchain, but some of us are still volunteers... and getting
older every day...
There is a patch backlog neither of us have even looked at, sorry. I'm
willing to put some time into this, but I think you all realize the time
involved to adequately test this. I'm not sure I have enough disk space. :-)
Personally, I tried to find funding to refactor DejaGnu in Python,
since Tcl is unmaintained too, but nobody was interested.
- rob -
---
https://www.senecass.com
next prev parent reply other threads:[~2020-05-14 15:16 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 10:26 DejaGnu/GCC testsuite behavior regarding multiple 'dg-do' Thomas Schwinge
2020-05-13 16:51 ` dejagnu version update? Mike Stump
2020-05-13 17:43 ` Jonathan Wakely
2020-05-13 18:29 ` Rainer Orth
2020-05-13 23:43 ` Maciej W. Rozycki
2020-05-14 14:08 ` Rainer Orth
2020-05-14 15:12 ` Rob Savoye [this message]
2020-05-14 16:08 ` David Edelsohn
2020-05-14 16:45 ` Rob Savoye
2020-05-14 18:11 ` Tom Tromey
2020-05-16 0:22 ` Mike Stump
2020-05-16 0:47 ` Rob Savoye
2020-05-15 1:50 ` Jacob Bachmeyer
2020-05-14 23:34 ` Maciej W. Rozycki
2020-05-15 0:33 ` Rob Savoye
2020-05-16 23:45 ` Maciej W. Rozycki
2020-05-17 3:30 ` Siddhesh Poyarekar
2020-05-17 3:48 ` Rob Savoye
2020-05-17 4:09 ` Andrew Pinski
2020-05-17 19:43 ` Maciej W. Rozycki
2020-05-17 19:55 ` Rob Savoye
2020-05-27 0:55 ` Rob Savoye
2020-05-27 1:20 ` Maciej W. Rozycki
2020-05-27 1:55 ` Rob Savoye
2020-06-09 20:12 ` Maciej W. Rozycki
2020-06-10 2:33 ` Jacob Bachmeyer
2020-06-10 4:18 ` dejagnu version update? [CORRECTION: not a regression in DejaGnu; GDB testsuite bug] Jacob Bachmeyer
2020-06-10 16:37 ` Maciej W. Rozycki
2020-06-11 2:43 ` GDB testsuite overrides default_target_compile and breaks Jacob Bachmeyer
2020-06-12 16:28 ` dejagnu version update? Christophe Lyon
2020-05-14 15:46 ` Maciej W. Rozycki
2020-05-14 6:44 ` Christophe Lyon
2020-05-14 8:45 ` Jonathan Wakely
2020-05-13 18:20 ` Rob Savoye
-- strict thread matches above, loose matches on Subject: below --
2017-08-25 13:25 David Edelsohn
2017-08-25 13:33 ` H.J. Lu
2017-08-25 13:35 ` David Edelsohn
2017-08-25 13:50 ` H.J. Lu
2017-08-25 13:50 ` David Edelsohn
2017-08-25 13:55 ` Rainer Orth
2017-08-25 17:47 ` David Edelsohn
2017-08-25 18:33 ` Winfried Magerl
2017-09-06 18:49 ` Jonathan Wakely
2017-09-06 19:19 ` David Edelsohn
[not found] <1441916913-11547-1-git-send-email-dmalcolm@redhat.com>
[not found] ` <1441916913-11547-3-git-send-email-dmalcolm@redhat.com>
[not found] ` <55F720E6.7020709@redhat.com>
[not found] ` <4CB1399A-23A6-44F7-A25F-ECBD953E03A0@gmail.com>
[not found] ` <55F74C3D.50504@redhat.com>
2015-09-15 19:21 ` Mike Stump
2015-09-15 19:23 ` David Malcolm
2015-09-15 20:11 ` Jeff Law
2015-09-15 20:51 ` Bernhard Reutner-Fischer
2017-05-13 10:24 ` Bernhard Reutner-Fischer
2017-05-13 10:38 ` Jakub Jelinek
2017-05-13 20:39 ` Jeff Law
2017-05-14 22:10 ` NightStrike
2017-05-15 8:06 ` Richard Biener
2017-05-15 19:18 ` Mike Stump
2017-05-15 20:41 ` Andreas Schwab
2017-05-16 9:54 ` Jonathan Wakely
2017-05-16 12:13 ` Bernhard Reutner-Fischer
2017-05-16 12:16 ` Jonathan Wakely
2017-05-16 12:35 ` Bernhard Reutner-Fischer
2017-05-16 18:34 ` Matthias Klose
2017-05-16 19:08 ` Mike Stump
2018-08-04 16:32 ` Bernhard Reutner-Fischer
2018-08-06 14:33 ` Jonathan Wakely
2018-08-06 15:26 ` Mike Stump
2018-08-07 16:34 ` Segher Boessenkool
2018-08-08 11:18 ` Bernhard Reutner-Fischer
2018-08-08 13:35 ` Richard Earnshaw (lists)
2018-08-08 14:37 ` Michael Matz
2018-08-08 16:45 ` Segher Boessenkool
2021-10-27 23:00 ` Bernhard Reutner-Fischer
2021-10-28 19:11 ` Jeff Law
2015-09-15 19:25 ` Bernhard Reutner-Fischer
2015-09-15 20:05 ` Jeff Law
2015-09-15 23:28 ` Mike Stump
2015-09-16 8:18 ` Andreas Schwab
2015-09-16 16:20 ` Mike Stump
2015-09-16 16:32 ` Ramana Radhakrishnan
2015-09-16 16:48 ` Jeff Law
2015-09-16 17:38 ` Trevor Saunders
2017-05-15 15:54 ` Martin Jambor
2017-05-15 18:05 ` Pedro Alves
2015-09-16 17:57 ` David Malcolm
2015-09-16 19:35 ` Bernhard Reutner-Fischer
2015-09-16 20:22 ` Mike Stump
2015-09-17 2:28 ` Segher Boessenkool
2015-09-17 15:15 ` Richard Earnshaw
2015-09-16 18:13 ` Mike Stump
2015-09-16 19:02 ` Bernhard Reutner-Fischer
2015-09-16 19:43 ` Ramana Radhakrishnan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=274e2a71-ddb0-18cc-70c1-4ca9ccf8bd29@welcomehome.org \
--to=rob@welcomehome.org \
--cc=dejagnu@gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=macro@wdc.com \
--cc=mikestump@comcast.net \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=thomas@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).