public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/108321] [13 regression] g++.dg/contracts/contracts-tmpl-spec2.C fails after r13-4160-g2efb237ffc68ec
Date: Mon, 09 Jan 2023 10:02:42 +0000 [thread overview]
Message-ID: <bug-108321-4-fYB9AaOEZn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108321-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108321
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
> 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"
This is fixed after r13-4290-g138ee8f7453ffd.
next prev parent reply other threads:[~2023-01-09 10:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 23:26 [Bug c++/108321] New: " seurer at gcc dot gnu.org
2023-01-09 10:02 ` marxin at gcc dot gnu.org [this message]
2023-01-10 7:11 ` [Bug c++/108321] " rguenth at gcc dot gnu.org
2023-01-10 7:11 ` rguenth at gcc dot gnu.org
2023-05-18 21:58 ` seurer at gcc dot gnu.org
2023-05-18 22:00 ` seurer at gcc dot gnu.org
2023-11-03 21:19 ` ewlu at rivosinc dot com
2023-11-24 1:43 ` pinskia at gcc dot gnu.org
2023-11-24 1:54 ` [Bug c++/108321] " pinskia at gcc dot gnu.org
2023-11-26 3:01 ` cvs-commit at gcc dot gnu.org
2023-11-26 3:02 ` pinskia at gcc dot gnu.org
2024-02-07 17:35 ` cvs-commit at gcc dot gnu.org
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=bug-108321-4-fYB9AaOEZn@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).