Commit 15bf6f3a by Ralf Wildenhues Committed by Ralf Wildenhues

docs: fix Function Attributes table nesting.

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

From-SVN: r170555
parent 9dfd4d1c
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> 2011-02-27 Jakub Jelinek <jakub@redhat.com>
PR middle-end/47903 PR middle-end/47903
......
...@@ -3291,8 +3291,6 @@ int core2_func (void) __attribute__ ((__target__ ("arch=core2"))); ...@@ -3291,8 +3291,6 @@ int core2_func (void) __attribute__ ((__target__ ("arch=core2")));
int sse3_func (void) __attribute__ ((__target__ ("sse3"))); int sse3_func (void) __attribute__ ((__target__ ("sse3")));
@end smallexample @end smallexample
@table @samp
@item i386 target attributes
On the 386, the following options are allowed: On the 386, the following options are allowed:
@table @samp @table @samp
...@@ -3435,8 +3433,8 @@ Specify which floating point unit to use. The ...@@ -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")} option must be specified as
@code{target("fpmath=sse+387")} because the comma would separate @code{target("fpmath=sse+387")} because the comma would separate
different options. different options.
@end table
@item PowerPC target attributes
On the PowerPC, the following options are allowed: On the PowerPC, the following options are allowed:
@table @samp @table @samp
...@@ -3608,8 +3606,6 @@ you do specify the @code{target("cpu=@var{CPU}")} attribute, ...@@ -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 compilation will tune for the @var{CPU} architecture, and not the
default tuning specified on the command line. default tuning specified on the command line.
@end table @end table
@end table
@end table
On the 386/x86_64 and PowerPC backends, you can use either multiple On the 386/x86_64 and PowerPC backends, you can use either multiple
strings to specify multiple options, or you can separate the option strings to specify multiple options, or you can separate the option
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment