bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug admin/10763] New: variable defined inside code in elf32-i386.c


From: jerker dot back at gmail dot com
Subject: [Bug admin/10763] New: variable defined inside code in elf32-i386.c
Date: 13 Oct 2009 10:38:06 -0000

Previously also reported to the binutils mailing list
This patch I believe explains the problem

===================================================================
RCS file: /cvs/src/src/bfd/elf32-i386.c,v
retrieving revision 1.225
diff -w -b -B -u -p -r1.225 elf32-i386.c
--- elf32-i386.c        9 Sep 2009 21:38:57 -0000       1.225
+++ elf32-i386.c        13 Oct 2009 02:16:33 -0000
@@ -4251,13 +4251,14 @@ elf_i386_finish_dynamic_symbol (bfd *out
            }
          else
            {
+                 asection *plt;
              if (!h->pointer_equality_needed)
                abort ();
 
              /* For non-shared object, we can't use .got.plt, which
                 contains the real function addres if we need pointer
                 equality.  We load the GOT entry with the PLT entry.  */
-             asection *plt = htab->elf.splt ? htab->elf.splt : htab->elf.iplt;
+             plt = htab->elf.splt ? htab->elf.splt : htab->elf.iplt;
              bfd_put_32 (output_bfd,
                          (plt->output_section->vma
                           + plt->output_offset + h->plt.offset),

-- 
           Summary: variable defined inside code in elf32-i386.c
           Product: binutils
           Version: 2.21 (HEAD)
            Status: NEW
          Severity: normal
          Priority: P2
         Component: admin
        AssignedTo: drow at sources dot redhat dot com
        ReportedBy: jerker dot back at gmail dot com
                CC: bug-binutils at gnu dot org
 GCC build triplet: x86_64-unknown-interix6.1
  GCC host triplet: x86_64-unknown-interix6.1
GCC target triplet: x86_64-unknown-interix6.1


http://sourceware.org/bugzilla/show_bug.cgi?id=10763

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]