Movatterモバイル変換

9.3.1 Legacy Type Encoding ¶

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

• the read-only qualifier of the pointee gets emitted before the ’^’.The read-only qualifier of the pointer itself gets ignored, unless itis a typedef. Also, the ’r’ is only emitted for the outermost type.
• 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 apointer.
• enums are always encoded as ’i’ (int) even if they are actuallyunsigned or long.

In addition to that, the NeXT runtime uses a different encoding forbitfields. It encodes them asb followed by the size, withouta bit offset or the underlying field type.