This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: x86 Q: why aren't the SSE intrinsics always_inline?
- From: Daniel Jacobowitz <drow at false dot org>
- To: Andrew Haley <aph at redhat dot com>
- Cc: gcc at gcc dot gnu dot org, gdb-discuss at gnu dot org, gdb at sourceware dot org
- Date: Tue, 14 Jun 2005 10:55:52 -0400
- Subject: Re: x86 Q: why aren't the SSE intrinsics always_inline?
- References: <96B69900-04F0-406A-9B53-F74B6D2B8071@apple.com> <17070.41423.645043.983123@zapata.pink>
[Redirecting off the misnamed gdb-discuss list; please use
gdb@sourceware instead.]
On Tue, Jun 14, 2005 at 10:22:23AM +0100, Andrew Haley wrote:
> You have the same problem with Java -- you're stepping through a Java
> program, and all of a sudden you're inside the memory allocator. What
> we _really_ need is some way to tell gdb "I'm debugging my own
> program, not the library" or somesuch. Or, and this is less
> desirable, some way to persuade gcc not to output debug info inside
> some inlined functions, although I can't image how a priori you'd
> decide which ones.
It'd be better to handle this in gdb than in gcc, sure. There's two
parts: better support for inline functions, which is already on the gdb
roadmap, and then some way of selecting which ones to ignore. And for
that latter, I have no idea how it should look...
--
Daniel Jacobowitz
CodeSourcery, LLC