From: Eli Zaretskii <eliz@gnu.org>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: msnyder@vmware.com, brobecker@adacore.com, dewar@adacore.com,
jreiver@free.fr, gdb@sourceware.org
Subject: Re: how to examine data with compiler optimization option set?
Date: Wed, 03 Sep 2008 18:34:00 -0000 [thread overview]
Message-ID: <umyip6pvb.fsf@gnu.org> (raw)
In-Reply-To: <y0mljyaudzb.fsf@ton.toronto.redhat.com>
> Cc: Joel Brobecker <brobecker@adacore.com>, Robert Dewar <dewar@adacore.com>, "jreiver@free.fr" <jreiver@free.fr>, "gdb@sourceware.org" <gdb@sourceware.org>
> From: fche@redhat.com (Frank Ch. Eigler)
> Date: Tue, 02 Sep 2008 23:04:24 -0400
>
> You might be surprised. Some RH engineers are working along these
> lines. Being able to debug (<=> probe/trace) optimized code is
> becoming more and more important, and gcc is slowly getting into the
> mood to help.
I'll applaud this mood. When I started using GCC (it was v1.x back
then), being able to efficiently debug optimized code was one of GCC's
most attractive features. When that feature was lost in GCC 3.x, I
was quite shocked. I'd love to have that back again.
next prev parent reply other threads:[~2008-09-03 18:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 21:27 J R
2008-09-02 21:36 ` Robert Dewar
2008-09-02 21:45 ` jreiver
2008-09-02 21:50 ` Robert Dewar
2008-09-02 21:57 ` Joel Brobecker
2008-09-03 0:05 ` Michael Snyder
2008-09-03 1:53 ` Robert Dewar
2008-09-03 2:52 ` Daniel Jacobowitz
2008-09-03 14:35 ` Robert Dewar
2008-09-03 3:06 ` Frank Ch. Eigler
2008-09-03 4:37 ` Michael Snyder
2008-09-03 14:36 ` Robert Dewar
2008-09-03 18:34 ` Eli Zaretskii [this message]
2008-09-03 21:43 ` Robert Dewar
2008-09-04 8:01 ` Andreas Schwab
2008-09-04 10:53 ` Robert Dewar
2008-09-04 14:05 ` Paul Koning
2008-09-04 14:09 ` Robert Dewar
2008-09-04 14:15 ` Paul Koning
2008-09-04 14:17 ` Robert Dewar
2008-09-04 15:55 ` Eli Zaretskii
2008-09-04 18:13 ` Frank Ch. Eigler
2008-09-04 20:46 ` Ulrich Weigand
2008-09-03 0:04 ` Michael Snyder
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=umyip6pvb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=dewar@adacore.com \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=jreiver@free.fr \
--cc=msnyder@vmware.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