From a360f6ae9448b9aa5197f8739462db41eabf6367 Mon Sep 17 00:00:00 2001 From: Ineiev Date: Tue, 29 Apr 2025 11:36:27 +0000 Subject: [PATCH] * c.texi (Aliasing Type Rules): Fix a typo s/j/a/. --- c.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/c.texi b/c.texi index 373ac78..ec775ab 100644 --- a/c.texi +++ b/c.texi @@ -13214,7 +13214,7 @@ What do these rules say about the example in this subsection? For @code{foo.size} (equivalently, @code{a->size}), @var{t} is @code{int}. The type @code{float} is not allowed as an aliasing type by those rules, so @code{b->size} is not supposed to alias with -elements of @code{j}. Based on that assumption, GNU C makes a +elements of @code{a}. Based on that assumption, GNU C makes a permitted optimization that was not, in this case, consistent with what the programmer intended the program to do.