From 9f51da538376188b7ad282ab38d704eed871bd4e Mon Sep 17 00:00:00 2001 From: Martin Liska Date: Tue, 12 Jun 2018 16:41:10 +0200 Subject: [PATCH] Document IntegerRange in internal documentation. 2018-06-12 Martin Liska * doc/options.texi: Document IntegerRange. From-SVN: r261498 --- gcc/ChangeLog | 4 ++++ gcc/doc/options.texi | 5 +++++ 2 files changed, 9 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 0fb4ea82c50..610abcd8c0a 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2018-06-12 Martin Liska + + * doc/options.texi: Document IntegerRange. + 2018-06-12 Martin Liska * config/i386/i386.opt: Make MPX-related options as Deprecated. diff --git a/gcc/doc/options.texi b/gcc/doc/options.texi index 80f1bd38bc6..b3ca9f6fce6 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's parser +will check that value of an option is inclusively within the +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 -- 2.30.2