public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: IainS <developer@sandoe-acoustics.co.uk>
To: Richard Henderson <rth@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Mike Stump <mrs@gcc.gnu.org>
Subject: Re: [Patch Debug] Emit pubnames for reorder & partition case.
Date: Tue, 21 Dec 2010 14:11:00 -0000	[thread overview]
Message-ID: <E51DB404-5EAB-44CD-AEA6-2FB8EE8B3522@sandoe-acoustics.co.uk> (raw)
In-Reply-To: <73DBA321-188F-45F8-93EA-D823BC671455@sandoe-acoustics.co.uk>


On 20 Dec 2010, at 22:43, IainS wrote:

>
> On 20 Dec 2010, at 22:06, Richard Henderson wrote:
>
>> On 12/20/2010 01:49 PM, IainS wrote:
>>> what I'm after is
>>> (a) avoiding a name clash.
>>> (b) having a generated  tag which is clearly understandable to the  
>>> person debugging ..
>>>
>>> If I prefix (rather than the current post-fix) with  "__hot_" and
>>> "__cold_"  (or even __hot_partition_) that should be safe and not
>>> require the extra hoops?
>>
>> Yes, that should work.  I do question whether you want this symbol
>> to match up with the name generated in the "atom" patch though.
>
>
> Yes, I think that is a good idea - I will amend the other patch to  
> match this one, assuming Mike also OKs it,
> thanks, for your reviews,

I've now amended the darwf2 patch thus:

		  /* There is no real support in DW2 for this .. so we make
		     a work-around.  First, emit the pub name for the segment
		     containing the function label.  Then make and emit a
		     simplified subprogram DIE for the second segment with the
		     name pre-fixed by __hot/cold_sect_of_.  We use the same
		     linkage name for the second die so that gdb will find both
		     sections when given "b foo".  */

<snip>
		  if (fde->in_std_section)
		    {
		      name = concat ("__cold_sect_of_", name, NULL);

etc.

and the config/darwin.c patch to match this.

FAOD, are the two patches now OK to apply, assuming Mike is happy with  
the Darwin aspects?

thanks
Iain

  reply	other threads:[~2010-12-21 12:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 14:40 IainS
2010-12-20 21:45 ` Richard Henderson
2010-12-20 22:06   ` IainS
2010-12-20 22:29     ` Richard Henderson
2010-12-20 22:37       ` IainS
2010-12-20 22:43         ` Richard Henderson
2010-12-21  6:13           ` IainS
2010-12-21 14:11             ` IainS [this message]
2010-12-21 17:10               ` Richard Henderson
2010-12-23 20:55 ` Mike Stump
2011-01-07 14:12   ` IainS

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=E51DB404-5EAB-44CD-AEA6-2FB8EE8B3522@sandoe-acoustics.co.uk \
    --to=developer@sandoe-acoustics.co.uk \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=mrs@gcc.gnu.org \
    --cc=rth@redhat.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).