+2016-01-11 Yury Gribov <y.gribov@samsung.com>
+
+ PR 67425
+ * common.opt (frandom-seed): Fix parameter name.
+ * doc/invoke.texi (frandom-seed): Ditto and describe parameter.
+
2016-01-11 Tom de Vries <tom@codesourcery.com>
PR tree-optimization/69058
frandom-seed=
Common Joined RejectNegative Var(common_deferred_options) Defer
--frandom-seed=<number> Make compile reproducible using <number>.
+-frandom-seed=<string> Make compile reproducible using <string>.
; This switch causes the command line that was used to create an
; object file to be recorded into the object file. The exact format
-fmem-report -fpre-ipa-mem-report -fpost-ipa-mem-report -fprofile-arcs @gol
-fopt-info @gol
-fopt-info-@var{options}@r{[}=@var{file}@r{]} @gol
--frandom-seed=@var{number} -fsched-verbose=@var{n} @gol
+-frandom-seed=@var{string} -fsched-verbose=@var{n} @gol
-fsel-sched-verbose -fsel-sched-dump-cfg -fsel-sched-pipelining-verbose @gol
-fstack-usage -ftest-coverage -ftime-report -fvar-tracking @gol
-fvar-tracking-assignments -fvar-tracking-assignments-toggle @gol
ignored. Thus only @file{vec.miss} is produced which contains
dumps from the vectorizer about missed opportunities.
-@item -frandom-seed=@var{number}
+@item -frandom-seed=@var{string}
@opindex frandom-seed
This option provides a seed that GCC uses in place of
random numbers in generating certain symbol names
produce them. You can use the @option{-frandom-seed} option to produce
reproducibly identical object files.
-The @var{number} should be different for every file you compile.
+The @var{string} can either be a number (decimal, octal or hex) or an
+arbitrary string (in which case it's converted to a number by
+computing CRC32).
+
+The @var{string} should be different for every file you compile.
@item -fsched-verbose=@var{n}
@opindex fsched-verbose