diff options
author | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-10-28 01:00:31 +0000 |
---|---|---|
committer | jsm28 <jsm28@138bc75d-0d04-0410-961f-82ee72b054a4> | 2004-10-28 01:00:31 +0000 |
commit | 01e3cadf200741d5d9867ade943bb80743a00540 (patch) | |
tree | 33d94c787a6ded805929c1022260774aeed28551 /gcc/doc/extend.texi | |
parent | d436970fe8ffcc1addc0288b84581b289d3cf352 (diff) | |
download | gcc-01e3cadf200741d5d9867ade943bb80743a00540.tar.gz |
* doc/contrib.texi, doc/cpp.texi, doc/cppopts.texi,
doc/extend.texi, doc/gcov.texi, doc/install.texi, doc/invoke.texi,
doc/libgcc.texi, doc/md.texi, doc/passes.texi,
doc/sourcebuild.texi, doc/tm.texi: Improve Texinfo formatting.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@89725 138bc75d-0d04-0410-961f-82ee72b054a4
Diffstat (limited to 'gcc/doc/extend.texi')
-rw-r--r-- | gcc/doc/extend.texi | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gcc/doc/extend.texi b/gcc/doc/extend.texi index 0667540ade3..45653b12277 100644 --- a/gcc/doc/extend.texi +++ b/gcc/doc/extend.texi @@ -1667,7 +1667,7 @@ attribute is ignored for virtual methods to allow creation of vtables using thunks. On the SH Symbian OS target the @code{dllimport} attribute also has -another affect - it can cause the vtable and run-time type information +another affect---it can cause the vtable and run-time type information for a class to be exported. This happens when the class has a dllimport'ed constructor or a non-inline, non-pure virtual function and, for either of those two conditions, the class also has a inline @@ -2780,7 +2780,7 @@ return normally. @opindex fno-common The @code{common} attribute requests GCC to place a variable in ``common'' storage. The @code{nocommon} attribute requests the -opposite -- to allocate space for it directly. +opposite---to allocate space for it directly. These attributes override the default chosen by the @option{-fno-common} and @option{-fcommon} flags respectively. @@ -3159,7 +3159,7 @@ attribute on all @code{enum} definitions. In the following example @code{struct my_packed_struct}'s members are packed closely together, but the internal layout of its @code{s} member -is not packed -- to do that, @code{struct my_unpacked_struct} would need to +is not packed---to do that, @code{struct my_unpacked_struct} would need to be packed too. @smallexample |