local symbol 0: discarded in section `.exit.text' from

local symbol 0: discarded in section `.exit.text' from

[Andrew Morton]

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.



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?

Thanks.

Re: local symbol 0: discarded in section `.exit.text' from drivers/built-in.o

[Jesse Barnes]

[-- Attachment #1: Type: text/plain, Size: 851 bytes --]

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?

H.J. said he'd fix it when he had time, I think it involves a rewrite of the 
dependency checking code in binutils.  I ended up compiling binutils with 
this hack to avoid the checks altogether.

Jesse


[-- Attachment #2: binutils-nodvcheck.patch --]
[-- Type: text/plain, Size: 522 bytes --]

--- binutils-2.14.90.0.8.orig/gas/config/tc-ia64.c	Wed Jan 14 13:07:45 2004
+++ binutils-2.14.90.0.8/gas/config/tc-ia64.c	Wed Jan 14 15:02:24 2004
@@ -6452,11 +6452,11 @@
 
     case 'x':
       /* -X conflicts with an ignored option, use -x instead */
-      md.detect_dv = 1;
+      md.detect_dv = 0;
       if (!arg || strcmp (arg, "explicit") == 0)
 	{
 	  /* set default mode to explicit */
-	  md.default_explicit_mode = 1;
+	  md.default_explicit_mode = 0;
 	  break;
 	}
       else if (strcmp (arg, "auto") == 0)

Re: local symbol 0: discarded in section `.exit.text' from

[Randy.Dunlap]

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)

Re: local symbol 0: discarded in section `.exit.text' from drivers/built-in.o

[David Mosberger]

>>>>> 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