public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nrk at disroot dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/104288] New: Null pointer check invalidly deleted Date: Sun, 30 Jan 2022 10:09:15 +0000 [thread overview] Message-ID: <bug-104288-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104288 Bug ID: 104288 Summary: Null pointer check invalidly deleted Product: gcc Version: 11.2.1 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: nrk at disroot dot org Target Milestone: --- Hi, In the following code, the null checks are removed when compiled with `-O2` on gcc v11.2.1. Compiling with `-O2 -fno-delete-null-pointer-checks` produces proper result. #include <stdbool.h> #include <stdio.h> #include <stdlib.h> #include <string.h> #define RESULT_PASS "PASS" #define RESULT_FAIL "FAIL" void test_assert(bool result) { printf("Assert: %s\n", result ? RESULT_PASS : RESULT_FAIL); if (!result) exit(EXIT_FAILURE); } void test_strcmp(const char *value_1, const char *value_2) { test_assert(value_1 != NULL); test_assert(value_2 != NULL); bool result = !strcmp(value_1, value_2); printf("Test equal: %s\n", result ? RESULT_PASS : RESULT_FAIL); } int main() { test_strcmp(NULL, "value 1"); } (code snippet taken from: https://gist.github.com/novns/c84d6e1efd6304b3076811fef34096fd )
next reply other threads:[~2022-01-30 10:09 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-30 10:09 nrk at disroot dot org [this message] 2022-01-30 10:26 ` [Bug middle-end/104288] [11/12 Regression] " pinskia at gcc dot gnu.org 2022-01-30 10:29 ` [Bug tree-optimization/104288] [11/12 Regression] EVRP null pointer check removal for strcmp (and maybe others) is not flow senative pinskia at gcc dot gnu.org 2022-01-30 11:03 ` jakub at gcc dot gnu.org 2022-01-31 8:21 ` rguenth at gcc dot gnu.org 2022-01-31 14:53 ` amacleod at redhat dot com 2022-01-31 15:34 ` jakub at gcc dot gnu.org 2022-01-31 22:39 ` amacleod at redhat dot com 2022-02-01 8:04 ` rguenther at suse dot de 2022-02-02 21:52 ` amacleod at redhat dot com 2022-02-08 15:03 ` cvs-commit at gcc dot gnu.org 2022-02-09 14:10 ` cvs-commit at gcc dot gnu.org 2022-02-09 14:11 ` amacleod at redhat dot com 2023-04-09 3:59 ` christian.prochaska@genode-labs.com 2023-04-09 4:12 ` pinskia at gcc dot gnu.org 2023-04-09 4:12 ` pinskia at gcc dot gnu.org 2023-04-09 7:07 ` christian.prochaska@genode-labs.com 2023-04-09 7:43 ` 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-104288-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: 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).