public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/111264] [14 regression] gcc.dg/plugin/analyzer_cpython_plugin.c breaks after r14-3580-g597b9ec69bca8a
Date: Fri, 01 Sep 2023 19:01:10 +0000	[thread overview]
Message-ID: <bug-111264-4-W8SOs9YTvi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111264-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Hans-Peter Nilsson <hp@gcc.gnu.org>:

https://gcc.gnu.org/g:d3dd69706af4c086cb3385ff1f321887b91f49fb

commit r14-3631-gd3dd69706af4c086cb3385ff1f321887b91f49fb
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Fri Sep 1 04:36:03 2023 +0200

    testsuite: Fix analyzer_cpython_plugin.c declarations, PR testsuite/111264

    Also, add missing newline at end of file.

            PR testsuite/111264
            * gcc.dg/plugin/analyzer_cpython_plugin.c: Make declarations
            C++11-compatible.

  parent reply	other threads:[~2023-09-01 19:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 23:22 [Bug other/111264] New: " seurer at gcc dot gnu.org
2023-09-01  2:09 ` [Bug other/111264] " hp at gcc dot gnu.org
2023-09-01  2:52 ` hp at gcc dot gnu.org
2023-09-01  3:07 ` pinskia at gcc dot gnu.org
2023-09-01  7:07 ` [Bug analyzer/111264] " rguenth at gcc dot gnu.org
2023-09-01 13:30 ` hp at gcc dot gnu.org
2023-09-01 18:59 ` [Bug testsuite/111264] " hp at gcc dot gnu.org
2023-09-01 19:01 ` cvs-commit at gcc dot gnu.org [this message]
2023-09-01 19:10 ` hp at gcc dot gnu.org
2023-09-01 19:11 ` hp at gcc dot gnu.org
2023-09-01 21:32 ` efric 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-111264-4-W8SOs9YTvi@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).