This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] invoke.texi, -mno-sum-in-toc (powerpc)


When I got linker warnings "relocation truncated to fit" on
powerpc64-linux I didn't realize they meant I had overflowed the TOC and
so I skipped over the descriptions of the options that I needed.  Would
it be appropriate to mention the actual linker message?

Tested with "make dvi" and "make info".  OK for the mainline and
3.2-branch?

2002-11-07  Janis Johnson  <janis187@us.ibm.com>

	* doc/invoke.texi (-mfull-toc): Add example of linker warning for
	overflowing the TOC space.

Index: invoke.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/invoke.texi,v
retrieving revision 1.198
diff -u -p -r1.198 invoke.texi
--- invoke.texi	1 Nov 2002 20:25:35 -0000	1.198
+++ invoke.texi	7 Nov 2002 17:21:04 -0000
@@ -6764,8 +6764,9 @@ each unique non-automatic variable refer
 will also place floating-point constants in the TOC@.  However, only
 16,384 entries are available in the TOC@.
 
-If you receive a linker error message that saying you have overflowed
-the available TOC space, you can reduce the amount of TOC space used
+If you receive a linker error message saying that you have overflowed
+the available TOC space, such as ``relocation truncated to fit''
+for a TOC entry, you can reduce the amount of TOC space used
 with the @option{-mno-fp-in-toc} and @option{-mno-sum-in-toc} options.
 @option{-mno-fp-in-toc} prevents GCC from putting floating-point
 constants in the TOC and @option{-mno-sum-in-toc} forces GCC to


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]