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 analyzer/111289] [13 Regression] Unwarranted -Wanalyzer-va-arg-type-mismatch warning
Date: Thu, 28 Mar 2024 18:32:53 +0000	[thread overview]
Message-ID: <bug-111289-4-RiUD2I3MNd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111289-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #7 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by John David Anglin <danglin@gcc.gnu.org>:

https://gcc.gnu.org/g:86b0b1bec6790f84b7a56fcef2a0a6c8cd91ffef

commit r14-9714-g86b0b1bec6790f84b7a56fcef2a0a6c8cd91ffef
Author: John David Anglin <danglin@gcc.gnu.org>
Date:   Thu Mar 28 18:32:12 2024 +0000

    Fix failure of c-c++-common/analyzer/stdarg-pr111289-int.c on hpux

    2024-03-28  John David Anglin  <danglin@gcc.gnu.org>

    gcc/testsuite/ChangeLog:

            PR analyzer/111289
            * c-c++-common/analyzer/stdarg-pr111289-int.c: Don't include
            <limits.h>.

  parent reply	other threads:[~2024-03-28 18:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05  0:02 [Bug analyzer/111289] New: " bruno at clisp dot org
2024-02-15 21:12 ` [Bug analyzer/111289] [13/14 Regression] " dmalcolm at gcc dot gnu.org
2024-02-19 23:10 ` cvs-commit at gcc dot gnu.org
2024-02-19 23:16 ` [Bug analyzer/111289] [13 " dmalcolm at gcc dot gnu.org
2024-02-24  2:58 ` danglin at gcc dot gnu.org
2024-03-24 19:41 ` danglin at gcc dot gnu.org
2024-03-24 20:26 ` bruno at clisp dot org
2024-03-28 18:32 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-14  5:22 ` 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-111289-4-RiUD2I3MNd@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).