[Bug translation/89915] clean up and canonicalize wording in params.def

["pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89915

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
           Keywords|                            |internal-improvement
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2022-12-04

--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>* some parameter descriptions still contain redundant comments. I complained about this one year ago in #79632, but nothing has happened since then.

That was fixed in GCC 10 when they were moved to param.opt.


To expand on this part here:
> params should be considered as internal options which only should be used for debugging and not even documented in the normal documentation.

The documentation in invoke.texi has the following:
```
@item --param @var{name}=@var{value}
@opindex param
In some places, GCC uses various constants to control the amount of
optimization that is done.  For example, GCC does not inline functions
that contain more than a certain number of instructions.  You can
control some of these constants on the command line using the
@option{--param} option.

The names of specific parameters, and the meaning of the values, are
tied to the internals of the compiler, and are subject to change
without notice in future releases.
```

Now saying that, the descriptions in params.opt could use improvements as I
mentioned before so confirmed.