Replace '`' symbol with double-quote in comments

* doc/README.win32: Replace "`" symbol (and paring single-quote) with
double-quote symbol.
* dyn_load.c (GC_register_dynlib_callback): Likewise.
* finalize.c (GC_should_invoke_finalizers): Likewise.
* include/private/gc_priv (GC_INLINE, ptr_t): Likewise.
* include/private/gcconfig.h (DATAEND): Likewise.

diff --git a/doc/README.win32 b/doc/README.win32
index d14686dd5df609f9890a8fe8035e43b9fc5734e0..471126e251044354b0cb05b263f54f02e06872dc 100644 (file)
--- a/doc/README.win32
+++ b/doc/README.win32
@@ -134,7 +134,7 @@ To compile the collector and testing programs use the command:
 All programs using gc should be compiled with 4-byte alignment.
 For further explanations on this see comments about Borland.
 
-If the gc is compiled as dll, the macro ``GC_DLL'' should be defined before
+If the gc is compiled as dll, the macro "GC_DLL" should be defined before
 including "gc.h" (for example, with -DGC_DLL compiler option). It's
 important, otherwise resulting programs will not run.
 

diff --git a/dyn_load.c b/dyn_load.c
index b1ec60145fe2e00aebd07107824ce95768f7446a..9d9700fee53f9580988f4cb0de6613d9776f6c87 100644 (file)
--- a/dyn_load.c
+++ b/dyn_load.c
@@ -446,7 +446,7 @@ STATIC int GC_register_dynlib_callback(struct dl_phdr_info * info,
         case PT_GNU_RELRO:
         /* This entry is known to be constant and will eventually be remapped
            read-only.  However, the address range covered by this entry is
-           typically a subset of a previously encountered `LOAD' segment, so
+           typically a subset of a previously encountered "LOAD" segment, so
            we need to exclude it.  */
         {
             int j;

diff --git a/finalize.c b/finalize.c
index 63696699cd777f7ef53b5127a2b317c20d6d5fa2..0ca956a464bfc81fe995994acb7b6b125933b0a7 100644 (file)
--- a/finalize.c
+++ b/finalize.c
@@ -954,7 +954,7 @@ GC_INNER void GC_finalize(void)
 #endif /* !JAVA_FINALIZATION_NOT_NEEDED */
 
 /* Returns true if it is worth calling GC_invoke_finalizers. (Useful if */
-/* finalizers can only be called from some kind of `safe state' and     */
+/* finalizers can only be called from some kind of "safe state" and     */
 /* getting into that safe state is expensive.)                          */
 GC_API int GC_CALL GC_should_invoke_finalizers(void)
 {

diff --git a/include/private/gc_priv.h b/include/private/gc_priv.h
index 58b22e1bf65bc9e0dbb7ced0aeac18f09c20a72a..f800f090f107b463af2494158e5570742c4cb357 100644 (file)
--- a/include/private/gc_priv.h
+++ b/include/private/gc_priv.h
@@ -145,7 +145,7 @@ typedef char * ptr_t;   /* A generic pointer to which we can add        */
 #endif /* __GNUC__ */
 
 #ifdef HAVE_CONFIG_H
-  /* The `inline' keyword as determined by Autoconf's `AC_C_INLINE'.    */
+  /* The "inline" keyword is as determined by Autoconf's AC_C_INLINE.   */
 # define GC_INLINE static inline
 #elif defined(_MSC_VER) || defined(__INTEL_COMPILER) || defined(__DMC__) \
         || defined(__WATCOMC__)
@@ -233,7 +233,7 @@ typedef char * ptr_t;   /* A generic pointer to which we can add        */
                     /* 1. There are probably no interesting, portable,  */
                     /*    strictly ANSI conforming C programs.          */
                     /* 2. This option makes it hard for the collector   */
-                    /*    to allocate space that is not ``pointed to''  */
+                    /*    to allocate space that is not "pointed to"    */
                     /*    by integers, etc.  Under SunOS 4.X with a     */
                     /*    statically linked libc, we empirically        */
                     /*    observed that it would be difficult to        */

diff --git a/include/private/gcconfig.h b/include/private/gcconfig.h
index c21c38ca32f258692e10e54e0b1c96b9f155e765..ceceb5b0f72c263c2bafa4f95c11e60880e39d5f 100644 (file)
--- a/include/private/gcconfig.h
+++ b/include/private/gcconfig.h
@@ -600,11 +600,11 @@
  * On UNIX-like systems, the collector will scan the area between DATASTART
  * and DATAEND for root pointers.
  *
- * DATAEND, if not `end' where `end' is defined as ``extern int end[];''.
+ * DATAEND, if not "end", where "end" is defined as "extern int end[]".
  * RTH suggests gaining access to linker script synth'd values with
- * this idiom instead of `&end' where `end' is defined as ``extern int end;'' .
- * Otherwise, ``GCC will assume these are in .sdata/.sbss'' and it will, e.g.,
- * cause failures on alpha*-*-* with ``-msmall-data or -fpic'' or mips-*-*
+ * this idiom instead of "&end", where "end" is defined as "extern int end".
+ * Otherwise, "GCC will assume these are in .sdata/.sbss" and it will, e.g.,
+ * cause failures on alpha*-*-* with -msmall-data or -fpic or mips-*-*
  * without any special options.
  *
  * STACKBOTTOM is the cool end of the stack, which is usually the