This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Xtensa port, part 4: documentation changes
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- To: Bob Wilson <bwilson at tensilica dot com>
- Cc: <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 30 Nov 2001 19:59:56 +0000 (GMT)
- Subject: Re: Xtensa port, part 4: documentation changes
On Fri, 30 Nov 2001, Bob Wilson wrote:
> + @emph{Xtensa Options}
> + -mbig-endian -mlittle-endian
This list should be inside @gccoptlist and with lines terminated with
@gol. This is to support manpage generation.
> + The Xtensa architecture is designed to support many different
> + configurations. The compiler's default options can be set to match a
> + particular Xtensa configuration by copying a configuration file into the
> + GCC sources when building GCC. The @samp{-m} options below may be used
"@." for full stops at ends of sentences following a capital letter.
> + @table @code
This should be @table @gcctabopt.
> + @item -mbig-endian
> + @itemx -mlittle-endian
In general, options need indexing with @opindex.
> + Enable or disable use of the optional normalization shift amount
> + (@code{NSA}) instructions to implement the built-in @samp{ffs} function.
@code{ffs}.
> + @item -mfused-madd
> + @itemx -mno-fused-madd
> + Enable or disable use of fused multiply/add and multiply/subtract
> + instructions in the floating-point option. This has no effect if the
Just a note, we should probably implement the C99 fma functions as
built-in functions (which expand to such an instruction if available,
otherwise just call the external library function). The default for this
option should depend on the FP_CONTRACT pragma - which however we don't
yet support.
> + The default is @samp{-mserialize-@-volatile}. Use
> + @samp{-mno-@-serialize-@-volatile} to omit the @code{MEMW} instructions.
The option names in the text should be the same as those in the @item
lines, inside @option (not @samp). Do you actually need discretionary
hyphens here?
> + Control the treatment of literal pools. The default is
> + @samp{--no-@-text-@-section-@-literals}, which places literals in a
> + separate section in the output file. This allows the literal pool to be
> + placed in a data RAM/ROM, and it also allows the linker to combine literal
> + pools from separate object files to remove redundant literals and
> + improve code size. With @samp{--text-@-section-@-literals}, the
Likewise.
--
Joseph S. Myers
jsm28@cam.ac.uk