From: Paul Koning <pkoning@equallogic.com>
To: eager@eagercon.com
Cc: drow@mvista.com, carlton@bactrian.org, gdb@sources.redhat.com
Subject: Re: breakpoints in constructors
Date: Wed, 30 Apr 2003 19:11:00 -0000 [thread overview]
Message-ID: <16048.11717.562000.96623@gargle.gargle.HOWL> (raw)
In-Reply-To: <3EB01CC8.CD952D8B@eagercon.com>
>>>>> "Michael" == Michael Eager <eager@eagercon.com> writes:
Michael> I think that you can generate a jump rather than a call, so
Michael> there is no extraneous call frame on the stack. (I think
Michael> that's what the Apple patch does, actually.)
You can jump in the same cases where you can use multiple entry
points: function A does some stuff and then finishes by doing what B
does. But if function A starts with what B does and then does
something else (e.g., the deleting constructor) then you can't jump.
Actually, if you pretend it's all calls, the optimizer will already
turn some of them into jumps ("tail call") automagically.
paul
next prev parent reply other threads:[~2003-04-30 19:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-18 20:04 David Carlton
2003-04-24 14:50 ` Daniel Jacobowitz
2003-04-24 22:02 ` Paul Koning
2003-04-25 0:30 ` Daniel Jacobowitz
2003-04-29 20:45 ` Paul Koning
2003-04-29 21:24 ` Daniel Jacobowitz
2003-04-30 19:04 ` Michael Eager
2003-04-30 19:11 ` Paul Koning [this message]
2003-04-30 19:19 ` Daniel Jacobowitz
2003-04-30 4:36 Michael Elizabeth Chastain
2003-04-30 5:20 ` Daniel Berlin
2003-04-30 14:44 Michael Elizabeth Chastain
2003-05-01 2:13 ` Daniel Berlin
2005-12-15 14:06 Breakpoints " Amit Kale
2005-12-26 7:52 ` Amit Kale
2005-12-27 4:07 ` Jim Blandy
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=16048.11717.562000.96623@gargle.gargle.HOWL \
--to=pkoning@equallogic.com \
--cc=carlton@bactrian.org \
--cc=drow@mvista.com \
--cc=eager@eagercon.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).