From 14285fc0bc43f33f529486063efdfea97615d1c1 Mon Sep 17 00:00:00 2001 From: Jim Meyering Date: Mon, 28 Aug 2006 05:52:44 +0000 Subject: [PATCH] * visibility.texi: Actually read and correct the grammar of the sentence affected by yesterday's change. --- doc/ChangeLog | 5 +++++ doc/visibility.texi | 6 +++--- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/doc/ChangeLog b/doc/ChangeLog index 77d336f9cc..45ebd40a4e 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,3 +1,8 @@ +2006-08-28 Jim Meyering + + * visibility.texi: Actually read and correct the grammar of the + sentence affected by yesterday's change. + 2006-08-27 Jim Meyering * visibility.texi: Remove duplicate word: "pointer". diff --git a/doc/visibility.texi b/doc/visibility.texi index 285236100d..881f33aa21 100644 --- a/doc/visibility.texi +++ b/doc/visibility.texi @@ -1,6 +1,6 @@ @c Documentation of gnulib module 'visibility'. -@c Copyright (C) 2005 Free Software Foundation, Inc. +@c Copyright (C) 2005, 2006 Free Software Foundation, Inc. @c Permission is granted to copy, distribute and/or modify this document @c under the terms of the GNU Free Documentation License, Version 1.2 or @@ -41,8 +41,8 @@ with the same name in the executable or in a shared library interposed 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 -to the variable's memory. So the code to access it is two memory +fetches a pointer in the so-called GOT (global offset table); this is a +pointer 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