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: Ian Lance Taylor <iant at google 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: Mon, 28 Jul 2008 20:17:33 -0700
- Subject: Re: frameworklet to assess the quality of debug information
- References: <or7ib5r8mb.fsf@oliva.athome.lsd.ic.unicamp.br>
Alexandre Oliva <aoliva@redhat.com> writes:
> 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? :-)
It's an interesting approach. Have you considered an approach more
like Dejagnu's dg support? It would be harder to write tests, but
would permit testing debugging info less invasively.
int
main (int argc, char *argv[])
{
int i = argc+1;
int j = argc-2;
int k = 5;
/* { gualchk argc 1 } */
/* { gualchk i 2 } */
/* { gualchk j -1 } */
}
Ian