This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
[PATCH] Document IntegerRange in internal documentation.
- From: Martin Liška <mliska at suse dot cz>
- To: gcc-patches at gcc dot gnu dot org
- Date: Tue, 12 Jun 2018 16:24:33 +0200
- Subject: [PATCH] Document IntegerRange in internal documentation.
Hi.
The patch is mentioning IntegerRange in documentation.
Ready for trunk?
Martin
gcc/ChangeLog:
2018-06-12 Martin Liska <mliska@suse.cz>
* doc/options.texi: Document IntegerRange.
---
gcc/doc/options.texi | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/gcc/doc/options.texi b/gcc/doc/options.texi
index 69743125c22..f30f077983f 100644
--- a/gcc/doc/options.texi
+++ b/gcc/doc/options.texi
@@ -264,6 +264,11 @@ option handler. @code{UInteger} should also be used on options like
@code{-falign-loops}=@var{n} are supported to make sure the saved
options are given a full integer.
+@item IntegerRange(@var{n}, @var{m})
+The options's arguments are integer numbers. The option parser
+will check that value of an option is inclusively withing
+range [@var{n}, @var{m}].
+
@item ToLower
The option's argument should be converted to lowercase as part of
putting it in canonical form, and before comparing with the strings