Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: fnf@specifix.com
Cc: Richard Sandiford <richard@codesourcery.com>,
	  gcc-patches@gcc.gnu.org,  gdb-patches@sourceware.org
Subject: Re: [RFC] Passing MIPS debug hints between gcc and gdb
Date: Thu, 18 May 2006 00:04:00 -0000	[thread overview]
Message-ID: <446B96F9.2070609@codesourcery.com> (raw)
In-Reply-To: <200605171624.16372.fnf@specifix.com>

Fred Fish wrote:
> On Thursday 11 May 2006 02:57, Richard Sandiford wrote:
>> Using empty sections was always a hack, to be honest (modelled on the
>> old .gcc_compiled_v3 thing, whatever it was called).  I suppose we
>> should be using note sections really.
> 
> Wouldn't that be ELF specific, as well as requiring the linker to
> merge hint strings?  I'm a little unclear on just what capabilities
> the current linker has to merge section contents so that "hint
> strings" put into a note section wouldn't be duplicated in the final
> linked output, one for each compilation unit.

The ARM EABI contains a specification for object-file attributes,
including rules about how to merge them.  The specification is quite
general; there are mechanisms for compiler extension, etc.

It is indeed ELF-specific, but I would guess you could use the same
technique on other object formats that allow additional sections.

I'm not sure what the current state of support for this feature is in
Binutils, but I think we should consider using the ARM strategy on all
platforms without a previously defined mechanism of their own; we want
it anyhow (for ARM), and we can presumably avoid duplicate effort/code
by reusing the code.

-- 
Mark Mitchell
CodeSourcery
mark@codesourcery.com
(650) 331-3385 x713


  reply	other threads:[~2006-05-17 21:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10 16:05 Fred Fish
2006-05-11  6:57 ` Richard Sandiford
2006-05-11 10:16   ` Fred Fish
2006-05-17 20:32   ` Fred Fish
2006-05-18  0:04     ` Mark Mitchell [this message]
2006-05-18 16:53       ` Richard Sandiford
2006-06-12 10:10   ` Fred Fish
2006-06-12 11:07     ` Richard Sandiford
2006-06-13 16:08     ` Fred Fish
2006-06-13 17:42       ` Daniel Jacobowitz

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=446B96F9.2070609@codesourcery.com \
    --to=mark@codesourcery.com \
    --cc=fnf@specifix.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=richard@codesourcery.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