This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: emit DW_AT_entry_pc for non-contiguous inlined functions
- From: Daniel Jacobowitz <drow at false dot org>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 28 Feb 2007 06:59:06 -0500
- Subject: Re: emit DW_AT_entry_pc for non-contiguous inlined functions
- References: <ork5y2g8wa.fsf@free.oliva.athome.lsd.ic.unicamp.br>
On Wed, Feb 28, 2007 at 02:15:33AM -0300, Alexandre Oliva wrote:
> Without this patch, whenever an inlined function is in non-contiguous
> blocks, we end up without any hint at its entry point whatsoever.
>
> This patch attempts to address that, but only emitting a
> DW_AT_entry_pc when the inlined function hasn't been combined and
> rearranged such that different portions thereof can be reached by
> independent code paths.
As it happens I've been working on inline functions for a few weeks.
I'd been going under the assumption that "entry PC" is a useless
concept for inline functions. What do you want to use it for, and
do you think it's available often enough to bother?
I see DWARF does mention it as a valid meaning of DW_AT_entry_pc,
so obviously someone agrees with you :-)
--
Daniel Jacobowitz
CodeSourcery