From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: fche@redhat.com (Frank Ch. Eigler)
Cc: eliz@gnu.org (Eli Zaretskii), schwab@suse.de (Andreas Schwab),
dewar@adacore.com, msnyder@vmware.com,
brobecker@adacore.com, jreiver@free.fr,
gdb@sourceware.org, aoliva@redhat.com (Alexandre Oliva)
Subject: Re: how to examine data with compiler optimization option set?
Date: Thu, 04 Sep 2008 20:46:00 -0000 [thread overview]
Message-ID: <200809042045.m84Kj4Yr013694@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20080904180918.GL19287@redhat.com> from "Frank Ch. Eigler" at Sep 04, 2008 02:09:18 PM
Frank Ch. Eigler wrote:
> On Thu, Sep 04, 2008 at 06:55:15PM +0300, Eli Zaretskii wrote:
> > [...]
> > > If parameters are passed in registers they are very likely to get lost.
> >
> > Then the compiler should, under -ggdb, emit code and debug info that
> > allow GDB finding these parameters somewhere.
>
> And it should.
Current GCC policy is that -g never changes anything in the emitted code.
If you build with and without -g and then strip the binaries, they are
supposed to be identical. This seems a useful property to me ...
However, this is not to say there couldn't be some other option that
did change code generation like that. (In any case, even without
changing code generation, there seems to be a lot of possibilities
to simply generate better debug info describing what's there!)
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2008-09-04 20:46 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
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 [this message]
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=200809042045.m84Kj4Yr013694@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=aoliva@redhat.com \
--cc=brobecker@adacore.com \
--cc=dewar@adacore.com \
--cc=eliz@gnu.org \
--cc=fche@redhat.com \
--cc=gdb@sourceware.org \
--cc=jreiver@free.fr \
--cc=msnyder@vmware.com \
--cc=schwab@suse.de \
/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