On 5/15/20 6:22 PM, Mike Stump wrote:
> Anyway, love to have software that can move code wholesale. Love to move the
> testsuite into a new language.
All it needs is funding. :-) What GDB needs is expect, not Tcl. Most
of the GDB testsuite is just expect pattern matching from the shell.
That's the entire reason I choose Tcl as it already had expect support.
Expect was necessary functionality for GDB testing. For GCC & Binutils,
Expect is only used for remote testing support.
As it's possible to embed Tcl in other programs, the idea was to use
an embedded Tcl interpreter when needed during a transition period. It's
mostly just the framework itself that would need to be refactored into
Python. There is also a large amount of code in gcc/testsuite that
should probably be in core DejaGnu too. That would be a large component
in analyzing existing code to write a true design doc. The best part is
now we have large toolchain testsuites to use to test DejaGnu changes.
A one point we thought DejaGnu would be used for other projects, but I
think it's obviously that these days it's only used for GNU toolchain
testing.
I'm making progress on setting up a development environment to test
patches. I use my ABE tool to build toolchains, had to fix some bugs
(and add PI support) first.
- rob -
---
https://www.senecass.com
