[m-rev.] for review: optimization_options.m

[Zoltan Somogyi]

2020-09-28 17:06 GMT+10:00 "Zoltan Somogyi" <zoltan.somogyi at runbox.com>:
> A related issue is: if an optimization level setting causes an integer option
> to be set to e.g. 3, then the current code handles a latter setting of that option
> to a higher value just fine (using int.max), but ignores any later setting of that
> option to a lower value.
> 
> I will fix this by applying the max *only* to option settings implicit in -O<n>
> arguments, not when a specific option is set explicitly. Again, in a separate
> diff for further review.

Here is that diff, for post-commit review by Peter.

Zoltan.