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/107807] gcc.dg/analyzer/errno-1.c FAILs
Date: Tue, 22 Nov 2022 22:32:47 +0000 [thread overview]
Message-ID: <bug-107807-4-jt1zIR7hrO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107807-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107807
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:
https://gcc.gnu.org/g:7c9717fcb5cf94ce1e7ef5c903058adf9980ff28
commit r13-4247-g7c9717fcb5cf94ce1e7ef5c903058adf9980ff28
Author: David Malcolm <dmalcolm@redhat.com>
Date: Tue Nov 22 17:29:21 2022 -0500
analyzer: fix 'errno' on Solaris and OS X [PR107807]
gcc/analyzer/ChangeLog:
PR analyzer/107807
* region-model-impl-calls.cc (register_known_functions): Register
"___errno" and "__error" as synonyms for "__errno_location".
gcc/testsuite/ChangeLog:
PR analyzer/107807
* gcc.dg/analyzer/errno-___errno.c: New test.
* gcc.dg/analyzer/errno-__error.c: New test.
* gcc.dg/analyzer/errno-global-var.c: New test.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-11-22 22:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 12:03 [Bug analyzer/107807] New: " ro at gcc dot gnu.org
2022-11-22 12:04 ` [Bug analyzer/107807] " ro at gcc dot gnu.org
2022-11-22 13:16 ` dmalcolm at gcc dot gnu.org
2022-11-22 13:23 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-11-22 15:14 ` dmalcolm at gcc dot gnu.org
2022-11-22 22:32 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-22 22:41 ` dmalcolm at gcc dot gnu.org
2022-11-24 8:53 ` ro at gcc dot gnu.org
2022-11-27 21:26 ` ro at CeBiTec dot Uni-Bielefeld.DE
2022-11-28 16:07 ` dmalcolm 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-107807-4-jt1zIR7hrO@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).