diff options
author | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-06-14 22:51:18 +0000 |
---|---|---|
committer | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2001-06-14 22:51:18 +0000 |
commit | 8e5fcce7d8664a0dc8dace24342d1061e27b478f (patch) | |
tree | 772b2cba97c73b14b62229c62b3429bd6ff1e4c1 /gcc/doc/objc.texi | |
parent | 83d63967c166f24347c6ef594df6c2e1def4317a (diff) | |
download | gcc-8e5fcce7d8664a0dc8dace24342d1061e27b478f.tar.gz |
* doc/c-tree.texi, doc/contrib.texi, doc/extend.texi,
doc/gcc.texi, doc/install.texi, doc/invoke.texi, doc/md.texi,
doc/objc.texi, doc/rtl.texi, doc/tm.texi: Fix spelling and typos.
Consistently use "built-in" and "bit-field". Minor logical markup
improvements.
* doc/gcc.1: Regenerate.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@43383 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/objc.texi')
-rw-r--r-- | gcc/doc/objc.texi | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/gcc/doc/objc.texi b/gcc/doc/objc.texi index 7e0aae12d10..21b1fd0a105 100644 --- a/gcc/doc/objc.texi +++ b/gcc/doc/objc.texi @@ -216,23 +216,23 @@ The types are encoded in the following way: @tab @code{*} @item unknown type @tab @code{?} -@item bitfields -@tab @code{b} followed by the starting position of the bitfield, the type of the bitfield and the size of the bitfield (the bitfields encoding was changed from the NeXT's compiler encoding, see below) +@item bit-fields +@tab @code{b} followed by the starting position of the bit-field, the type of the bit-field and the size of the bit-field (the bit-fields encoding was changed from the NeXT's compiler encoding, see below) @end multitable @c @sp 1 -The encoding of bitfields has changed to allow bitfields to be properly +The encoding of bit-fields has changed to allow bit-fields to be properly handled by the runtime functions that compute sizes and alignments of -types that contain bitfields. The previous encoding contained only the -size of the bitfield. Using only this information it is not possible to -reliably compute the size occupied by the bitfield. This is very +types that contain bit-fields. The previous encoding contained only the +size of the bit-field. Using only this information it is not possible to +reliably compute the size occupied by the bit-field. This is very important in the presence of the Boehm's garbage collector because the objects are allocated using the typed memory facility available in this collector. The typed memory allocation requires information about where the pointers are located inside the object. -The position in the bitfield is the position, counting in bits, of the +The position in the bit-field is the position, counting in bits, of the bit closest to the beginning of the structure. The non-atomic types are encoded as follows: |