From: "Randy.Dunlap" <rddunlap@osdl.org>
To: linux-ia64@vger.kernel.org
Subject: Re: local symbol 0: discarded in section `.exit.text' from
Date: Thu, 08 Apr 2004 20:12:07 +0000 [thread overview]
Message-ID: <20040408131207.3f3975fb.rddunlap@osdl.org> (raw)
In-Reply-To: <20040408003018.42418a33.akpm@osdl.org>
On Thu, 8 Apr 2004 00:30:18 -0700 Andrew Morton wrote:
|
| For some reason the ia64 toolchain like to find these...
|
| linux-tiger:/usr/src/25> reference_discarded.pl
| Finding objects, 1137 objects, ignoring 0 module(s)
| Finding conglomerates, ignoring 119 conglomerate(s)
| Scanning objects
| Error: ./drivers/scsi/qla2xxx/ql2100.o .debug_info refers to 0000000000011fef DIR64LSB .exit.text
| Error: ./drivers/scsi/qla2xxx/ql2100.o .debug_info refers to 0000000000012310 DIR64LSB .exitcall.exit
| Error: ./drivers/scsi/qla2xxx/ql2100.o .debug_line refers to 000000000000069d DIR64LSB .exit.text
| Error: ./drivers/scsi/qla2xxx/ql2100.o .debug_aranges refers to 0000000000000030 DIR64LSB .exit.text
| Error: ./drivers/scsi/qla2xxx/ql2200.o .debug_info refers to 0000000000011fef DIR64LSB .exit.text
| Error: ./drivers/scsi/qla2xxx/ql2200.o .debug_info refers to 0000000000012310 DIR64LSB .exitcall.exit
| Error: ./drivers/scsi/qla2xxx/ql2200.o .debug_line refers to 000000000000069d DIR64LSB .exit.text
| Error: ./drivers/scsi/qla2xxx/ql2200.o .debug_aranges refers to 0000000000000030 DIR64LSB .exit.text
|
| Can anyone suggest what has actually caused this to happen? I have
| CONFIG_DEBUG_INFO=n.
I don't see those with gcc 3.3.1, but maybe my 'reference_discarded.pl'
script isn't good enough.
Is yours from: http://www.kernelnewbies.org/scripts/ ?
| Using gcc (GCC) 3.5.0 20040206 (experimental)
|
|
| 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?
Yep, I see those too. :(
--
~Randy
"We have met the enemy and he is us." -- Pogo (by Walt Kelly)
(Again. Sometimes I think ln -s /usr/src/linux/.config .signature)
next prev parent reply other threads:[~2004-04-08 20:12 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 ` Randy.Dunlap [this message]
2004-04-08 23:38 ` David Mosberger
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=20040408131207.3f3975fb.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--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