This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: frameworklet to assess the quality of debug information
- From: "Joseph S. Myers" <joseph at codesourcery dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, Andrew MacLeod <amacleod at redhat dot com>, Janis Johnson <janis187 at us dot ibm dot com>, Richard Guenther <richard dot guenther at gmail dot com>, Michael Matz <matz at suse dot de>, Daniel Jacobowitz <drow at false dot org>
- Date: Tue, 29 Jul 2008 02:00:19 +0000 (UTC)
- Subject: Re: frameworklet to assess the quality of debug information
- References: <or7ib5r8mb.fsf@oliva.athome.lsd.ic.unicamp.br>
On Mon, 28 Jul 2008, Alexandre Oliva wrote:
> Here's my first cut at trying to tell how well or how bad we perform
> in terms of debug info, that can be dropped into the GCC run-time test
> infrastructure and used by means of #include in new tests that add
> GUALCHK* annotations (or with separate compilation, if some stuff is
> moved into a separate header).
>
> Thoughts, comments, suggestions, tomatoes, eggs? :-)
For the GCC testsuite parts of this will of course need to be written in
Tcl to use the DejaGnu interfaces to execute both the debugger (on a
possibly remote host) and the test program (on a possibly remote,
simulator, etc. target), rather than fork/exec. (For experimenting with
different approaches, assessing the current state of the compiler, etc.,
this isn't needed so much.)
--
Joseph S. Myers
joseph@codesourcery.com