From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
To: bosch@gnat.com
Cc: haible@ilog.fr, rth@cygnus.com, gcc@gcc.gnu.org
Subject: Re: tail call optimization vs. debugging
Date: Sat, 25 Mar 2000 12:54:00 -0000 [thread overview]
Message-ID: <200003252050.VAA26012@loewis.home.cs.tu-berlin.de> (raw)
In-Reply-To: <20000325171727.D8EFD34D80@nile.gnat.com>
> One of the main things that IMO needs to be preserved, even when it
> would mean loosing some optimizations at -O2, is being able to
> reliably breakpoint on functions and get useful stack tracebacks
> with arguments.
Does this mean you don't want the compiler to support the inline
keyword? Because with inlining, you cannot set a break-point on an
inlined function, and get a useful stack backtrace with arguments
right now.
Martin
next prev parent reply other threads:[~2000-03-25 12:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-25 9:17 Geert Bosch
2000-03-25 11:35 ` Richard Henderson
2000-03-25 12:54 ` Martin v. Loewis [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-25 13:08 Geert Bosch
2000-03-25 14:07 ` Richard Henderson
2000-03-24 12:39 Bruno Haible
2000-03-24 14:03 ` Daniel Berlin+list.gcc
2000-03-24 14:24 ` Richard Henderson
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=200003252050.VAA26012@loewis.home.cs.tu-berlin.de \
--to=martin@loewis.home.cs.tu-berlin.de \
--cc=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=haible@ilog.fr \
--cc=rth@cygnus.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).