* Tail Calls & Insight
@ 2000-05-16 12:43 Duane Ellis
2000-05-16 12:47 ` Tom Tromey
0 siblings, 1 reply; 2+ messages in thread
From: Duane Ellis @ 2000-05-16 12:43 UTC (permalink / raw)
To: insight
I'm working on a custom port for insight/gdb for our custom RISC cpu
and I'm having a problem with something.
When you click the 'next' button, GDB really single steps till the PC
goes somewhere expected, or unexpected.
If it's unexpected (ie: a subroutine call occurs) GDB then assumes
that the return address is on the stack and pops the return address,
sets a new breakpoint and 'runs', hoping it will hit the breakpoint.
Unfortunatly, (or fortunatly depending on your view) one optmization
trick we use is to convert tail calls into jumps.
Is there any way of describing this situation to GDB?
-Duane.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Tail Calls & Insight
2000-05-16 12:43 Tail Calls & Insight Duane Ellis
@ 2000-05-16 12:47 ` Tom Tromey
0 siblings, 0 replies; 2+ messages in thread
From: Tom Tromey @ 2000-05-16 12:47 UTC (permalink / raw)
To: duane_ellis; +Cc: insight
Duane> Unfortunatly, (or fortunatly depending on your view) one
Duane> optmization trick we use is to convert tail calls into jumps.
Duane> Is there any way of describing this situation to GDB?
You should really ask this on the gdb list and not the Insight list.
I imagine it is possible, since gcc recently got this optimization.
However, I don't know the details.
Tom
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-05-16 12:47 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-05-16 12:43 Tail Calls & Insight Duane Ellis
2000-05-16 12:47 ` Tom Tromey
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).