public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: local symbol 0: discarded in section `.exit.text' from drivers/built-in.o
Date: Thu, 08 Apr 2004 23:38:02 +0000	[thread overview]
Message-ID: <16501.57946.120317.246675@napali.hpl.hp.com> (raw)
In-Reply-To: <20040408003018.42418a33.akpm@osdl.org>

>>>>> On Thu, 8 Apr 2004 08:32:34 -0700, Jesse Barnes <jbarnes@sgi.com> said:

  Jesse> On Thursday, April 8, 2004 12:30 am, Andrew Morton wrote:
  >> Also, I am heartily sick of this gunk from the assembler:

  >> {standard input}:20882: Warning: This is the location of the conflicting
  >> usage  {standard input}:20917: Warning: Use of 'ld4' may violate RAW
  >> dependency 'DBR#' (data) {standard input}:20917: Warning: Only the first
  >> path encountering the conflict is reported {standard input}:20882: Warning:
  >> This is the location of the conflicting usage {standard input}:20917:
  >> Warning: Use of 'ld4' may violate RAW dependency 'DBR#' (data)

  >> Has that been fixed yet?  If so, which is a good version of binutils to
  >> start using?

  Jesse> H.J. said he'd fix it when he had time, I think it involves a
  Jesse> rewrite of the dependency checking code in binutils.

I don't think it's a "fix" as much as a new feature.  AFAIK, there is
currently know way to say that those apparent RAWs really an
issue (because we're in kernel space and the breakpoints are setup
for user-level).

It probably would be good to have an assembler directive to turn off
dependency-checking.  A bit dangerous, but it's probably too complicated
to have more fine-grained control for all the system stuff.

  Jesse> I ended up compiling binutils with this hack to avoid the
  Jesse> checks altogether.

Rather dangerous.  I don't like the warnings either, but a missed true
dependency violation is even worse.  Just ask Don Dugger or Asit how
much fun they had tracking down such bugs before GAS supported the
dependency-checking.

	--david

      parent reply	other threads:[~2004-04-08 23:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-08  7:30 local symbol 0: discarded in section `.exit.text' from Andrew Morton
2004-04-08 15:32 ` local symbol 0: discarded in section `.exit.text' from drivers/built-in.o Jesse Barnes
2004-04-08 20:12 ` local symbol 0: discarded in section `.exit.text' from Randy.Dunlap
2004-04-08 23:38 ` David Mosberger [this message]

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=16501.57946.120317.246675@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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