From: Michael Meissner <meissner@gcc.gnu.org>
Date: Thu, 8 Aug 1996 22:26:12 +0000 (+0000)
Subject: Fix for G++ not knowing whether a vtable will be private or public when the TOC refer... 
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=581bc4de55b720e9d4b53d7ca6297d0f07b622ca;p=gcc.git

Fix for G++ not knowing whether a vtable will be private or public when the TOC reference is updated

From-SVN: r12605
---

diff --git a/gcc/config/rs6000/rs6000.c b/gcc/config/rs6000/rs6000.c
index 00ec109f87f..33a544c22ea 100644
--- a/gcc/config/rs6000/rs6000.c
+++ b/gcc/config/rs6000/rs6000.c
@@ -4128,7 +4128,23 @@ output_toc (file, x, labelno)
 
       fputs ("[TC],", file);
     }
-  output_addr_const (file, x);
+
+  /* Currently C++ toc references to vtables can be emitted before it
+     is decided whether the vtable is public or private.  If this is
+     the case, then the linker will eventually complain that there is
+     a TOC reference to an unknown section.  Thus, for vtables only,
+     we emit the TOC reference to reference the symbol and not the
+     section.  */
+  if (!strncmp ("_vt.", real_name, 4))
+    {
+      RS6000_OUTPUT_BASENAME (file, real_name);
+      if (offset < 0)
+	fprintf (file, "%d", offset);
+      else if (offset > 0)
+	fprintf (file, "+%d", offset);
+    }
+  else
+    output_addr_const (file, x);
   putc ('\n', file);
 }