OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs: fix Function Attributes table nesting.

Browse Source 
gcc/:
	* doc/extend.texi (Function Attributes): Avoid deeply (and
	wrongly) nested tables.

From-SVN: r170555
This commit is contained in:
Ralf Wildenhues 2011-02-28 06:35:43 +00:00 committed by Ralf Wildenhues
parent 9dfd4d1c3b
commit 15bf6f3af7
2 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -1,3 +1,8 @@
2011-02-28 Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
* doc/extend.texi (Function Attributes): Avoid deeply (and
wrongly) nested tables.
2011-02-27 Jakub Jelinek <jakub@redhat.com>
PR middle-end/47903

6
gcc/doc/extend.texi
View File

@ -3291,8 +3291,6 @@ int core2_func (void) __attribute__ ((__target__ ("arch=core2")));
int sse3_func (void) __attribute__ ((__target__ ("sse3")));
@end smallexample
@table @samp
@item i386 target attributes
On the 386, the following options are allowed:
@table @samp
@ -3435,8 +3433,8 @@ Specify which floating point unit to use. The
@code{target("fpmath=sse,387")} option must be specified as
@code{target("fpmath=sse+387")} because the comma would separate
different options.
@end table
@item PowerPC target attributes
On the PowerPC, the following options are allowed:
@table @samp
@ -3608,8 +3606,6 @@ you do specify the @code{target("cpu=@var{CPU}")} attribute,
compilation will tune for the @var{CPU} architecture, and not the
default tuning specified on the command line.
@end table
@end table
@end table
On the 386/x86_64 and PowerPC backends, you can use either multiple
strings to specify multiple options, or you can separate the option