From: Daniel Jacobowitz <drow@false.org>
To: Fred Fish <fnf@specifixinc.com>
Cc: Andrew Haley <aph@redhat.com>, gcc@gcc.gnu.org, gdb@sourceware.org
Subject: Re: [Gdb-discuss] Re: x86 Q: why aren't the SSE intrinsics always_inline?
Date: Wed, 15 Jun 2005 01:17:00 -0000 [thread overview]
Message-ID: <20050615011738.GA30673@nevyn.them.org> (raw)
In-Reply-To: <200506142112.39968.fnf@specifixinc.com>
[Redirecting off gdb-discuss again]
On Tue, Jun 14, 2005 at 09:12:39PM -0400, Fred Fish wrote:
> On Tuesday 14 June 2005 10:55, Daniel Jacobowitz wrote:
> > better support for inline functions, which is already on the gdb
> > roadmap
>
> Where's the roadmap? I'm just starting to look at this very issue
> and would be good to know what is planned or in progress.
I was being figurative :-) We already know we need to do it.
I already have a 30% or so hack which handles creating inline function
frames. It works well enough for simple backtraces. But the symbol
table side of it is all rotten, so it's not very useful - segfaults a
lot.
I also have the first 20% or so of setting breakpoints on multiple
locations implemented, which is a necessary partner to that. But
that's even less finished.
Ask me if you want either set of code. The latest version of the
latter is in the gdb-patches archive from early this year. I don't
think I ever posted the former - too gross.
If you want to work on anything without duplicating effort, it behooves
_you_ to discuss it on the mailing lists first.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-06-15 1:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96B69900-04F0-406A-9B53-F74B6D2B8071@apple.com>
[not found] ` <17070.41423.645043.983123@zapata.pink>
2005-06-14 14:56 ` Daniel Jacobowitz
2005-06-15 1:12 ` [Gdb-discuss] " Fred Fish
2005-06-15 1:17 ` Daniel Jacobowitz [this message]
2005-06-15 1:48 ` Fred Fish
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=20050615011738.GA30673@nevyn.them.org \
--to=drow@false.org \
--cc=aph@redhat.com \
--cc=fnf@specifixinc.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
/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