diff options
| author | Craig Jennings <c@cjennings.net> | 2024-04-07 13:41:34 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2024-04-07 13:41:34 -0500 |
| commit | 754bbf7a25a8dda49b5d08ef0d0443bbf5af0e36 (patch) | |
| tree | f1190704f78f04a2b0b4c977d20fe96a828377f1 /devdocs/gcc~13/legacy-type-encoding.html | |
new repository
Diffstat (limited to 'devdocs/gcc~13/legacy-type-encoding.html')
| -rw-r--r-- | devdocs/gcc~13/legacy-type-encoding.html | 10 |
1 files changed, 10 insertions, 0 deletions
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 @@ +<div class="subsection-level-extent" id="Legacy-type-encoding"> <div class="nav-panel"> <p> Next: <a href="_0040encode" accesskey="n" rel="next"><code class="code">@encode</code></a>, Up: <a href="type-encoding" accesskey="u" rel="up">Type Encoding</a> [<a href="index#SEC_Contents" title="Table of contents" rel="contents">Contents</a>][<a href="indices" title="Index" rel="index">Index</a>]</p> </div> <h1 class="subsection" id="Legacy-Type-Encoding"><span>8.3.1 Legacy Type Encoding<a class="copiable-link" href="#Legacy-Type-Encoding"> ¶</a></span></h1> <p>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: </p> <ul class="itemize mark-bullet"> <li>the read-only qualifier of the pointee gets emitted before the ’^’. The read-only qualifier of the pointer itself gets ignored, unless it is a typedef. Also, the ’r’ is only emitted for the outermost type. </li> +<li>32-bit longs are encoded as ’l’ or ’L’, but not always. For typedefs, the compiler uses ’i’ or ’I’ instead if encoding a struct field or a pointer. </li> +<li> +<code class="code">enum</code>s are always encoded as ’i’ (int) even if they are actually unsigned or long. </li> +</ul> <p>In addition to that, the NeXT runtime uses a different encoding for bitfields. It encodes them as <code class="code">b</code> followed by the size, without a bit offset or the underlying field type. </p> </div><div class="_attribution"> + <p class="_attribution-p"> + © Free Software Foundation<br>Licensed under the GNU Free Documentation License, Version 1.3.<br> + <a href="https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Legacy-type-encoding.html" class="_attribution-link">https://gcc.gnu.org/onlinedocs/gcc-13.1.0/gcc/Legacy-type-encoding.html</a> + </p> +</div> |