This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

undocumented optimization options


Several options reported by --help=optimize are not documented in the
GCC Manual (via invoke.texi) but are still reported with
--help=optimize,^undocumented.  Here are the options along with the
people who checked in the entries to common.opt:

  -fipa-cp               steven
  -fipa-matrix-reorg     razya
  -fipa-pure-const       zadeck  (enabled with -O)
  -fipa-reference        zadeck  (enabled with -O)
  -fipa-type-escape      zadeck
  -fvar-tracking-uninit  ctice

Is there a policy about whether an experimental option can be left
undocumented, or should it be documented with a statement that it is
experimental?

If an option is left undocumented on purpose then its entry in common.opt
should include "Undocumented".

Janis



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]