From: Jason Merrill <jason@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] c++: Fix up -fcontract* options
Date: Tue, 22 Nov 2022 10:09:06 -0500 [thread overview]
Message-ID: <493ff6ad-1498-2a79-dd5c-13b34a3d59ba@redhat.com> (raw)
In-Reply-To: <Y3wC9ytEbTC0OidM@tucnak>
On 11/21/22 18:00, Jakub Jelinek wrote:
> Hi!
>
> 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.
OK.
> 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.)?
True, but I think let's leave them alone for now, they'll probably all
be replaced as the feature specification evolves.
> 2022-11-21 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.
>
> --- gcc/c-family/c.opt.jj 2022-11-19 09:21:14.314444706 +0100
> +++ gcc/c-family/c.opt 2022-11-21 23:51:55.605736499 +0100
> @@ -1692,12 +1692,12 @@ EnumValue
> Enum(on_off) String(on) Value(1)
>
> fcontract-assumption-mode=
> -C++ Joined
> +C++ Joined RejectNegative
> -fcontract-assumption-mode=[on|off] Enable or disable treating axiom level contracts as assumptions (default on).
>
> fcontract-build-level=
> C++ Joined RejectNegative
> --fcontract-build-level=[off|default|audit] Specify max contract level to generate runtime checks for
> +-fcontract-build-level=[off|default|audit] Specify max contract level to generate runtime checks for.
>
> fcontract-strict-declarations=
> C++ Var(flag_contract_strict_declarations) Enum(on_off) Joined Init(0) RejectNegative
> @@ -1708,15 +1708,15 @@ C++ Var(flag_contract_mode) Enum(on_off)
> -fcontract-mode=[on|off] Enable or disable all contract facilities (default on).
>
> fcontract-continuation-mode=
> -C++ Joined
> +C++ Joined RejectNegative
> -fcontract-continuation-mode=[on|off] Enable or disable contract continuation mode (default off).
>
> fcontract-role=
> -C++ Joined
> +C++ Joined RejectNegative
> -fcontract-role=<name>:<semantics> Specify the semantics for all levels in a role (default, review), or a custom contract role with given semantics (ex: opt:assume,assume,assume)
>
> fcontract-semantic=
> -C++ Joined
> +C++ Joined RejectNegative
> -fcontract-semantic=<level>:<semantic> Specify the concrete semantics for level
>
> fcoroutines
>
> Jakub
>
next prev parent reply other threads:[~2022-11-22 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 23:00 Jakub Jelinek
2022-11-22 15:09 ` Jason Merrill [this message]
2022-11-24 10:58 ` [committed] c++: Further -fcontract* option description fixes Jakub Jelinek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=493ff6ad-1498-2a79-dd5c-13b34a3d59ba@redhat.com \
--to=jason@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).