public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: binutils@sources.redhat.com
Subject: Re: Empty section removal has messed up MIPS gdb
Date: Wed, 20 Apr 2005 21:57:00 -0000	[thread overview]
Message-ID: <20050420215746.GA32312@nevyn.them.org> (raw)
In-Reply-To: <20050420215317.GA18859@lucon.org>

On Wed, Apr 20, 2005 at 02:53:17PM -0700, H. J. Lu wrote:
> On Wed, Apr 20, 2005 at 05:35:33PM -0400, Daniel Jacobowitz wrote:
> > GCC used to leave a message for the debugger in the form of an empty
> > section:
> > 
> >       /* Generate a special section to describe the ABI switches used to
> >          produce the resultant binary.  This used to be done by the assembler
> >          setting bits in the ELF header's flags field, but we have run out of
> >          bits.  GDB needs this information in order to be able to correctly
> >          debug these binaries.  See the function mips_gdbarch_init() in
> >          gdb/mips-tdep.c.  This is unnecessary for the IRIX 5/6 ABIs and
> >          causes unnecessary IRIX 6 ld warnings.  */
> > 
> > The emitted bits were simply:
> > 
> > 	.section .mdebug.abi64
> > 	.previous
> > 
> > The sections are now stripped.  I don't want to put contents in them and
> > waste object file space unless it's absolutely necessary.  How should I
> > cajole ld into leaving them?
> > 
> 
> Mark it KEEP?

This is something that has to be done in the linker, right?  i.e. the
linker would also need to know about this convention.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

  reply	other threads:[~2005-04-20 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 21:35 Daniel Jacobowitz
2005-04-20 21:53 ` H. J. Lu
2005-04-20 21:57   ` Daniel Jacobowitz [this message]
2005-04-20 22:58     ` H. J. Lu
2005-04-20 23:58       ` Eric Christopher

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=20050420215746.GA32312@nevyn.them.org \
    --to=drow@false.org \
    --cc=binutils@sources.redhat.com \
    --cc=hjl@lucon.org \
    /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).