Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: Michael Snyder <msnyder@redhat.com>, Kevin Buettner <kevinb@redhat.com>
Cc: "David S. Miller" <davem@redhat.com>,
	gdb@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Kill SOFUN_ADDRESS_MAYBE_MISSING (was Re: multi-arch TODO)
Date: Tue, 23 Apr 2002 12:10:00 -0000	[thread overview]
Message-ID: <1020423191000.ZM9800@localhost.localdomain> (raw)
In-Reply-To: Michael Snyder <msnyder@redhat.com> "Re: [RFA] Kill SOFUN_ADDRESS_MAYBE_MISSING (was Re: multi-arch TODO)" (Apr 23, 10:46am)

On Apr 23, 10:46am, Michael Snyder wrote:

> Kevin Buettner wrote:
> > 
> > On Apr 23,  3:00am, David S. Miller wrote:
> > 
> > >    >   Why don't all Linux targets define this?  Do some binutils ports
> > >    >   perform this optimization and others not?  Or was there some bug
> > >    >   in N_FUN/N_SO stabs in binutils and/or gcc that this is papering
> > >    >   around?  kevinb@cyghat.com is the one who added this to powerpc
> > >    >   and i386 Linux.
> > >
> > >    I haven't given it a lot of thought recently, but my opinion is that
> > >    the SOFUN_ADDRESS_MAYBE_MISSING code ought to be enabled everywhere.
> > >    The only downside that I can think of is that we lose the ability
> > >    to put a symbol at address 0.
> > >
> > > Sounds find to me, how about this patch?
> > >
> > > 2002-04-23  David S. Miller  <davem@redhat.com>
> > >
> > >       * config/i386/tm-i386sol2.h, config/i386/tm-linux.h,
> > >       config/powerpc/tm-linux.h, config/powerpc/tm-ppc-eabi.h,
> > >       config/sparc/tm-sun4sol2.h (SOFUN_ADDRESS_MAYBE_MISSING): Kill.
> > >       * dbxread.c, elfread.c, minsyms.c, mdebugread.c, symmisc.c,
> > >       symtab.h (whole file): Act as if SOFUN_ADDRESS_MAYBE_MISSING was
> > >       always defined, kill ifdefs.
> > 
> > Yes, this is exactly what I had in mind.  It looks okay to me, but it
> > needs to be carefully considered and approved (or not) by the symtab
> > maintainers.
> > 
> > As noted earlier, the downside is that we lose the ability to put a
> > symbol at address 0.  This doesn't pose a problem for operating
> > systems which'll never map part of the program at address 0, but there
> > may be some embedded environments for which this is a concern.
> 
> Replace "may be" with "almost certainly are".

Agreed.

I'm beginning to remember more about this now.  Contrary to my previous
statements in this thread, I don't think we really lose the ability to
have symbols at address 0.  We can still have them, but it's more work
to figure out that they're at zero because the minimal symbols will be
consulted to make the determination.

Kevin


  reply	other threads:[~2002-04-23 19:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020422.040949.16307644.davem@redhat.com>
     [not found] ` <1020422152449.ZM1373@localhost.localdomain>
2002-04-23  3:10   ` David S. Miller
2002-04-23  6:52     ` Eli Zaretskii
2002-04-23  7:01       ` [RFA] Kill SOFUN_ADDRESS_MAYBE_MISSING David S. Miller
2002-04-23  9:05         ` Eli Zaretskii
2002-04-23  9:43     ` [RFA] Kill SOFUN_ADDRESS_MAYBE_MISSING (was Re: multi-arch TODO) Kevin Buettner
2002-04-23 10:58       ` Michael Snyder
2002-04-23 12:10         ` Kevin Buettner [this message]
2002-04-23 23:11           ` [RFA] Kill SOFUN_ADDRESS_MAYBE_MISSING David S. Miller
2002-04-23 12:05     ` [RFA] Kill SOFUN_ADDRESS_MAYBE_MISSING (was Re: multi-arch TODO) Elena Zannoni
2002-04-23 23:13       ` [RFA] Kill SOFUN_ADDRESS_MAYBE_MISSING David S. Miller
2002-04-24  1:03       ` David S. Miller
2002-04-24 17:40         ` Elena Zannoni
2002-04-24 17:53           ` David S. Miller
2002-04-24  1:13       ` David S. Miller

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=1020423191000.ZM9800@localhost.localdomain \
    --to=kevinb@redhat.com \
    --cc=davem@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=msnyder@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