public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Mark Wielaard <mark@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-9812] Regenerate common.opt.urls
Date: Fri,  5 Apr 2024 15:32:04 +0000 (GMT)	[thread overview]
Message-ID: <20240405153204.86FC53858C24@sourceware.org> (raw)

https://gcc.gnu.org/g:0c22f67526d72aa451633d5212259a8f75e59a44

commit r14-9812-g0c22f67526d72aa451633d5212259a8f75e59a44
Author: Mark Wielaard <mark@klomp.org>
Date:   Fri Apr 5 17:22:16 2024 +0200

    Regenerate common.opt.urls
    
    The new support for gcov modified condition/decision coverage
    introduced two new flags for gcc, -Wcoverage-too-many-conditions and
    -fcondition-coverage. But didn't regenerate the gcc/common.opt.urls.
    
    Fixes: 08a52331803f ("Add condition coverage (MC/DC)")
    
    gcc/ChangeLog:
    
            * common.opt.urls: Regenerate.

Diff:
---
 gcc/common.opt.urls | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/gcc/common.opt.urls b/gcc/common.opt.urls
index db4354989fc..f71ed80a34b 100644
--- a/gcc/common.opt.urls
+++ b/gcc/common.opt.urls
@@ -280,6 +280,9 @@ UrlSuffix(gcc/Warning-Options.html#index-Wcoverage-mismatch)
 Wcoverage-invalid-line-number
 UrlSuffix(gcc/Warning-Options.html#index-Wcoverage-invalid-line-number)
 
+Wcoverage-too-many-conditions
+UrlSuffix(gcc/Warning-Options.html#index-Wcoverage-too-many-conditions)
+
 Wmissing-profile
 UrlSuffix(gcc/Warning-Options.html#index-Wmissing-profile)
 
@@ -1057,6 +1060,9 @@ UrlSuffix(gcc/Instrumentation-Options.html#index-fprofile-abs-path)
 ;   duplicate: 'gcc/Instrumentation-Options.html#index-fprofile-arcs'
 ;   duplicate: 'gcc/Other-Builtins.html#index-fprofile-arcs-1'
 
+fcondition-coverage
+UrlSuffix(gcc/Instrumentation-Options.html#index-fcondition-coverage)
+
 fprofile-dir=
 UrlSuffix(gcc/Instrumentation-Options.html#index-fprofile-dir)

                 reply	other threads:[~2024-04-05 15:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240405153204.86FC53858C24@sourceware.org \
    --to=mark@gcc.gnu.org \
    --cc=gcc-cvs@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).