From 8f0a7a0bc384ff37d56e7bd91a7ad2ee872e87b8 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Sun, 27 Aug 2006 20:38:52 +0000 Subject: [PATCH] * visibility.texi: Remove duplicate word: "pointer". --- doc/ChangeLog | 4 ++++ doc/visibility.texi | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 27f4e939e2..77d336f9cc 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,7 @@ +2006-08-27 Jim Meyering + + * visibility.texi: Remove duplicate word: "pointer". + 2006-08-15 Paul Eggert * regexprops-generic.texi: Add a copyright notice. diff --git a/doc/visibility.texi b/doc/visibility.texi index 07e88361c1..285236100d 100644 --- a/doc/visibility.texi +++ b/doc/visibility.texi @@ -42,7 +42,7 @@ with @code{LD_PRELOAD}.) Whereas a call to a function for which the compiler can assume that it is in the same shared library is just a direct "call" instructions. Similarly for variables: A reference to a global variable fetches a pointer in the so-called GOT (global offset table); this pointer -pointer to the variable's memory. So the code to access it is two memory +to the variable's memory. So the code to access it is two memory load instructions. Whereas for a variable which is known to reside in the same shared library, it is just a direct memory access: one memory load instruction. -- 2.30.2