From 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Sun, 7 Apr 2024 13:41:34 -0500 Subject: new repository --- devdocs/gcc~13/legacy-type-encoding.html | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 devdocs/gcc~13/legacy-type-encoding.html (limited to 'devdocs/gcc~13/legacy-type-encoding.html') diff --git a/devdocs/gcc~13/legacy-type-encoding.html b/devdocs/gcc~13/legacy-type-encoding.html new file mode 100644 index 00000000..8842689a --- /dev/null +++ b/devdocs/gcc~13/legacy-type-encoding.html @@ -0,0 +1,10 @@ +

8.3.1 Legacy Type Encoding

Unfortunately, historically GCC used to have a number of bugs in its encoding code. The NeXT runtime expects GCC to emit type encodings in this historical format (compatible with GCC-3.3), so when using the NeXT runtime, GCC will introduce on purpose a number of incorrect encodings:

In addition to that, the NeXT runtime uses a different encoding for bitfields. It encodes them as b followed by the size, without a bit offset or the underlying field type.

+

+ © Free Software Foundation
Licensed under the GNU Free Documentation License, Version 1.3.
+ https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Legacy-type-encoding.html +

+
-- cgit v1.2.3