I checked Wikipedia and Wiktionary and it knows gibibyte but not
gigibyte.

The contribution guidelines say "you must perform make info and make dvi
and correct any errors".

Since I only did a sparse checkout of /contrib and /gcc, I couldn't do
that. Because I only changed a single letter in two places I hope this
wasn't necessary in this case.

Hope this is the correct way to send fixes for minor typos and that the
patch is fine. Of course, somebody other than me would have to commit
it.
From dd26752306e9ff350072f756b02cf4d02a95db98 Mon Sep 17 00:00:00 2001
From: Vanessa Heinbokel <anameisrequi...@proton.me>
Date: Tue, 17 Jun 2025 03:15:02 +0200
Subject: [PATCH] doc: Fix typo

This fixes a one-letter typo of the same word in two files.

gcc/ChangeLog:

	* doc/invoke.texi: Fix typo gigibyte -> gibibyte.
	* doc/options.texi: Same.

Signed-off-by: Vanessa Heinbokel <anameisrequi...@proton.me>
---
 gcc/doc/invoke.texi  | 2 +-
 gcc/doc/options.texi | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index dec3c7a..abd3531 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -131,7 +131,7 @@ threshold of some sort may be arbitrarily large decimal or hexadecimal
 integers followed by a byte size suffix designating a multiple of bytes
 such as @code{kB} and @code{KiB} for kilobyte and kibibyte, respectively,
 @code{MB} and @code{MiB} for megabyte and mebibyte, @code{GB} and
-@code{GiB} for gigabyte and gigibyte, and so on.  Such arguments are
+@code{GiB} for gigabyte and gibibyte, and so on.  Such arguments are
 designated by @var{byte-size} in the following text.  Refer to the NIST,
 IEC, and other relevant national and international standards for the full
 listing and explanation of the binary and decimal byte size prefixes.
diff --git a/gcc/doc/options.texi b/gcc/doc/options.texi
index b46b997..6a0a4c1 100644
--- a/gcc/doc/options.texi
+++ b/gcc/doc/options.texi
@@ -320,7 +320,7 @@ precision using saturation arithmetic in the corresponding type.  The argument
 may be followed by a @samp{byte-size} suffix designating a multiple of bytes
 such as @code{kB} and @code{KiB} for kilobyte and kibibyte, respectively,
 @code{MB} and @code{MiB} for megabyte and mebibyte, @code{GB} and @code{GiB}
-for gigabyte and gigibyte, and so on.  @code{ByteSize} should be used for
+for gigabyte and gibibyte, and so on.  @code{ByteSize} should be used for
 with options that take a very large argument representing a size in bytes,
 such as @option{-Wlarger-than=}.
 
-- 
2.49.0

Reply via email to