public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/107599] New: [13 regression] c-c++-common/diagnostic-format-json-4.c fails after r13-3853-g9c3bc557995463
Date: Wed, 09 Nov 2022 19:38:26 +0000	[thread overview]
Message-ID: <bug-107599-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107599

            Bug ID: 107599
           Summary: [13 regression]
                    c-c++-common/diagnostic-format-json-4.c fails after
                    r13-3853-g9c3bc557995463
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:9c3bc557995463fe1dcc37ec503af780a6c1a341, r13-3853-g9c3bc557995463

make  -k check-gcc
RUNTESTFLAGS="dg.exp=c-c++-common/diagnostic-format-json-4.c"
"]*#index-Wmisleading-indentation""t-json-4.c  -Wc++-compat   dg-regexp 45 not
found: ""option_url": "https:[^\n
FAIL: c-c++-common/diagnostic-format-json-4.c  -Wc++-compat  (test for excess
errors)
"]*#index-Wmisleading-indentation""t-json-4.c  -std=gnu++98  dg-regexp 45 not
found: ""option_url": "https:[^\n
FAIL: c-c++-common/diagnostic-format-json-4.c  -std=gnu++98 (test for excess
errors)
"]*#index-Wmisleading-indentation""t-json-4.c  -std=gnu++14  dg-regexp 45 not
found: ""option_url": "https:[^\n
FAIL: c-c++-common/diagnostic-format-json-4.c  -std=gnu++14 (test for excess
errors)
"]*#index-Wmisleading-indentation""t-json-4.c  -std=gnu++17  dg-regexp 45 not
found: ""option_url": "https:[^\n
FAIL: c-c++-common/diagnostic-format-json-4.c  -std=gnu++17 (test for excess
errors)
"]*#index-Wmisleading-indentation""t-json-4.c  -std=gnu++20  dg-regexp 45 not
found: ""option_url": "https:[^\n
FAIL: c-c++-common/diagnostic-format-json-4.c  -std=gnu++20 (test for excess
errors)

commit 9c3bc557995463fe1dcc37ec503af780a6c1a341 (HEAD, refs/bisect/bad)
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Nov 9 13:10:11 2022 +0100

    sphinx: update diagnostics URLs

             reply	other threads:[~2022-11-09 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09 19:38 seurer at gcc dot gnu.org [this message]
2022-11-09 19:40 ` [Bug c++/107599] " marxin at gcc dot gnu.org
2022-11-09 19:59 ` cvs-commit at gcc dot gnu.org
2022-11-09 19:59 ` marxin at gcc dot gnu.org
2022-11-28 22:17 ` pinskia 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-107599-4@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).