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/113150] FAIL: c-c++-common/analyzer/fd-glibc-byte-stream-socket.c -std=c++98 (test for excess errors) Date: Sun, 14 Jan 2024 18:24:38 +0000 [thread overview] Message-ID: <bug-113150-4-tVphWPAYMj@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113150-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113150 --- Comment #1 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:b468821eea8df4890157e816e924244810058cb5 commit r14-7232-gb468821eea8df4890157e816e924244810058cb5 Author: John David Anglin <danglin@gcc.gnu.org> Date: Sun Jan 14 18:23:51 2024 +0000 Skip several analyzer socket tests on hppa*-*-hpux* 2024-01-14 John David Anglin <danglin@gcc.gnu.org> gcc/testsuite/ChangeLog: PR analyzer/113150 * c-c++-common/analyzer/fd-glibc-byte-stream-socket.c: Skip on hppa*-*-hpux*. * c-c++-common/analyzer/fd-manpage-getaddrinfo-client.c: Likewise. * c-c++-common/analyzer/fd-mappage-getaddrinfo-server.c: Likewise. * c-c++-common/analyzer/fd-symbolic-socket.c: Likewise. * gcc.dg/analyzer/fd-glibc-byte-stream-connection-server.c: Likewise.
next prev parent reply other threads:[~2024-01-14 18:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-26 17:59 [Bug analyzer/113150] New: " danglin at gcc dot gnu.org 2024-01-14 18:24 ` cvs-commit at gcc dot gnu.org [this message] 2024-01-18 19:51 ` [Bug analyzer/113150] " iains at gcc dot gnu.org 2024-01-18 19:55 ` iains at gcc dot gnu.org 2024-03-04 13:05 ` [Bug analyzer/113150] [14 Regression] " rguenth at gcc dot gnu.org 2024-03-07 20:53 ` law at gcc dot gnu.org 2024-05-07 7:43 ` [Bug analyzer/113150] [14/15 " rguenth 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-113150-4-tVphWPAYMj@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: linkBe 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).