public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@sgi.com>
To: Dave Jones <davej@redhat.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Sam Ravnborg <sam@ravnborg.org>
Subject: Re: reference_discarded addition
Date: Sun, 08 Jan 2006 12:52:35 +1100	[thread overview]
Message-ID: <31103.1136685155@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Fri, 06 Jan 2006 02:40:19 CDT." <20060106074019.GA1226@redhat.com>

Dave Jones (on Fri, 6 Jan 2006 02:40:19 -0500) wrote:
>Error: ./fs/quota_v2.o .opd refers to 0000000000000020 R_PPC64_ADDR64    .exit.text
>
>Been carrying this for some time in Red Hat trees.
>
>Signed-off-by: Dave Jones <davej@redhat.com>
>
>diff -urNp --exclude-from=/home/davej/.exclude linux-3022/scripts/reference_discarded.pl linux-10000/scripts/reference_discarded.pl
>--- linux-3022/scripts/reference_discarded.pl
>+++ linux-10000/scripts/reference_discarded.pl
>@@ -88,6 +88,7 @@ foreach $object (keys(%object)) {
> 		    ($from !~ /\.text\.exit$/ &&
> 		     $from !~ /\.exit\.text$/ &&
> 		     $from !~ /\.data\.exit$/ &&
>+		     $from !~ /\.opd$/ &&
> 		     $from !~ /\.exit\.data$/ &&
> 		     $from !~ /\.altinstructions$/ &&
> 		     $from !~ /\.pdr$/ &&

For our future {in}sanity, add a comment that this is the ppc .opd
section, not the ia64 .opd section.  ia64 .opd should not point to
discarded sections.

Any idea why ppc .opd points to discarded sections when ia64 does not?
AFAICT no ia64 object has a useful .opd section, they are all empty or
(sometimes) a dummy entry which is 1 byte long.  ia64 .opd data is
built at link time, not compile time.

It is a pity that ppc is generating .opd entries at compile time.  It
makes it impossible to detect a real reference to a discarded function.


  reply	other threads:[~2006-01-08  1:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-06  7:40 reference_discarded addition Dave Jones
2006-01-08  1:52 ` Keith Owens [this message]
2006-01-08 17:59   ` Sam Ravnborg

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=31103.1136685155@ocs3.ocs.com.au \
    --to=kaos@sgi.com \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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