diff options
Diffstat (limited to 'gcc/config/frv')
| -rw-r--r-- | gcc/config/frv/frv.c | 2 | ||||
| -rw-r--r-- | gcc/config/frv/frv.h | 8 |
2 files changed, 5 insertions, 5 deletions
diff --git a/gcc/config/frv/frv.c b/gcc/config/frv/frv.c index 1b6f37b4934..cea0b571902 100644 --- a/gcc/config/frv/frv.c +++ b/gcc/config/frv/frv.c @@ -7858,7 +7858,7 @@ frv_adjust_field_align (field, computed) /* If this isn't a :0 field and if the previous element is a bitfield also, see if the type is different, if so, we will need to align the - bitfield to the next boundary */ + bit-field to the next boundary */ if (prev && ! DECL_PACKED (field) && ! integer_zerop (DECL_SIZE (field)) diff --git a/gcc/config/frv/frv.h b/gcc/config/frv/frv.h index 414fe2716ed..f5fe93ee0b6 100644 --- a/gcc/config/frv/frv.h +++ b/gcc/config/frv/frv.h @@ -688,13 +688,13 @@ extern int g_switch_set; /* whether -G xx was passed. */ /* Define this if you wish to imitate the way many other C compilers handle alignment of bitfields and the structures that contain them. - The behavior is that the type written for a bitfield (`int', `short', or + The behavior is that the type written for a bit-field (`int', `short', or other integer type) imposes an alignment for the entire structure, as if the structure really did contain an ordinary field of that type. In addition, - the bitfield is placed within the structure so that it would fit within such + the bit-field is placed within the structure so that it would fit within such a field, not crossing a boundary for it. - Thus, on most machines, a bitfield whose type is written as `int' would not + Thus, on most machines, a bit-field whose type is written as `int' would not cross a four-byte boundary, and would force four-byte alignment for the whole structure. (The alignment used may not be four bytes; it is controlled by the other alignment parameters.) @@ -711,7 +711,7 @@ extern int g_switch_set; /* whether -G xx was passed. */ `STRUCTURE_SIZE_BOUNDARY' as large as `BIGGEST_ALIGNMENT'. Then every structure can be accessed with fullwords. - Unless the machine has bitfield instructions or you define + Unless the machine has bit-field instructions or you define `STRUCTURE_SIZE_BOUNDARY' that way, you must define `PCC_BITFIELD_TYPE_MATTERS' to have a nonzero value. |