Re: frameworklet to assess the quality of debug information

2008-07-30 Thread Daniel Jacobowitz
On Mon, Jul 28, 2008 at 06:39:40PM -0300, 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* annotation

Re: frameworklet to assess the quality of debug information

2008-07-30 Thread Richard Guenther
On Tue, Jul 29, 2008 at 9:01 PM, Alexandre Oliva <[EMAIL PROTECTED]> wrote: > On Jul 29, 2008, "Richard Guenther" <[EMAIL PROTECTED]> wrote: > >> why not pair the testcase with a gdb script directly? > > Mostly a matter of convenience. Writing code and adding "test this > here, etc", and not havin

Re: frameworklet to assess the quality of debug information

2008-07-29 Thread Alexandre Oliva
On Jul 29, 2008, "Richard Guenther" <[EMAIL PROTECTED]> wrote: > why not pair the testcase with a gdb script directly? Mostly a matter of convenience. Writing code and adding "test this here, etc", and not having to adjust a testcase all over just because you have to add an #include feels so muc

Re: frameworklet to assess the quality of debug information

2008-07-29 Thread Alexandre Oliva
On Jul 29, 2008, Ian Lance Taylor <[EMAIL PROTECTED]> wrote: > Alexandre Oliva <[EMAIL PROTECTED]> 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 #inclu

Re: frameworklet to assess the quality of debug information

2008-07-29 Thread Richard Guenther
On Tue, Jul 29, 2008 at 5:17 AM, Ian Lance Taylor <[EMAIL PROTECTED]> wrote: > Alexandre Oliva <[EMAIL PROTECTED]> 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 b

Re: frameworklet to assess the quality of debug information

2008-07-28 Thread Ian Lance Taylor
Alexandre Oliva <[EMAIL PROTECTED]> 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

Re: frameworklet to assess the quality of debug information

2008-07-28 Thread Joseph S. Myers
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

Re: frameworklet to assess the quality of debug information

2008-07-28 Thread Alexandre Oliva
On Jul 28, 2008, Alexandre Oliva <[EMAIL PROTECTED]> wrote: > Thoughts, comments, suggestions, tomatoes, eggs? :-) >Contributed by Alexandre Oliva <[EMAIL PROTECTED]>. Heh. So now you know I copied the header from some other file :-) Fixed, th