Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fred Fish <fnf@specifix.com>
To: Richard Sandiford <richard@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [RFC] Passing MIPS debug hints between gcc and gdb
Date: Wed, 17 May 2006 20:32:00 -0000	[thread overview]
Message-ID: <200605171624.16372.fnf@specifix.com> (raw)
In-Reply-To: <87y7x9aw12.fsf@talisman.home>

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.

How about just creating common symbols, which will be merged.  That
takes up less space than a section in the executable file, but does
contribute something to the size of of the loaded uninitialized
segment.  I.E. if I add the following to mips_file_start():

      {
        char buf[32];
        sprintf (buf, "__%s", abi_string);
        mips_declare_common_object (asm_out_file, buf, "\n\t.comm\t", 4, 0, true);
      }

cc1 then generates:

        .comm   __abiO64,4,0

in each output.  The linker should then merge all these into a single
symbol in the output, which gdb could easily search for.

-Fred 


  parent reply	other threads:[~2006-05-17 20:23 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 [this message]
2006-05-18  0:04     ` Mark Mitchell
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=200605171624.16372.fnf@specifix.com \
    --to=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