diff options
| author | Jakub Jelinek <jakub@redhat.com> | 2022-11-23 09:29:04 +0100 |
|---|---|---|
| committer | Jakub Jelinek <jakub@redhat.com> | 2022-11-23 09:29:04 +0100 |
| commit | e1b503d7068cbaf4be938c02eb6686ea5a716fee (patch) | |
| tree | 7b00645e1733062b7241e2934c73f64619db6bda /maintainer-scripts/gcc_release | |
| parent | 3138db588a46d445876c0358df55fa3995c6f221 (diff) | |
| download | gcc-e1b503d7068cbaf4be938c02eb6686ea5a716fee.zip gcc-e1b503d7068cbaf4be938c02eb6686ea5a716fee.tar.gz gcc-e1b503d7068cbaf4be938c02eb6686ea5a716fee.tar.bz2 | |
c++: Fix up -fcontract* options
I've noticed
+FAIL: compiler driver --help=c++ option(s): "^ +-.*[^:.]\$" absent from output: " -fcontract-build-level=[off|default|audit] Specify max contract level to generate runtime checks for"
error, this is due to missing dot at the end of the description.
The second part of the first hunk should fix that, but while at it,
I find it weird that some options don't have RejectNegative, yet
for options that accept an argument a negative option looks weird
and isn't really handled.
Though, shall we have those [on|off] options at all?
Those are inconsistent with all other boolean options gcc has.
Every other boolean option is -fwhatever for it being on
and -fno-whatever for it being off, shouldn't the options be
without arguments and accept negatives (-fcontract-assumption-mode
vs. -fno-contract-assumption-mode etc.)?
2022-11-23 Jakub Jelinek <jakub@redhat.com>
* c.opt (fcontract-assumption-mode=, fcontract-continuation-mode=,
fcontract-role=, fcontract-semantic=): Add RejectNegative.
(fcontract-build-level=): Terminate description with dot.
Diffstat (limited to 'maintainer-scripts/gcc_release')
0 files changed, 0 insertions, 0 deletions