public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/109175] error: 'void* __builtin_memset(void*, int, long unsigned int)' writing 4 or more bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=] Date: Fri, 24 Mar 2023 18:46:49 +0000 [thread overview] Message-ID: <bug-109175-4-03tfnKKOSA@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109175-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109175 --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced all the way removing all of the classes showing exactly what I thought it was: ``` void *ao(); float *aq(long t) { if (t) return nullptr; return static_cast<float *>(ao()); } float v; void at(long t) { long a = sizeof(0), i = 0; auto b = aq(t); for (; i < a; ++i) b[i] = v; for (; i < t; ++i) b[i] = 0.0f; } ``` Notice how there is no check for null on aq.
next prev parent reply other threads:[~2023-03-24 18:46 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-17 14:52 [Bug c++/109175] New: " malat at debian dot org 2023-03-17 14:54 ` [Bug c++/109175] " malat at debian dot org 2023-03-17 14:55 ` malat at debian dot org 2023-03-17 15:04 ` malat at debian dot org 2023-03-20 19:50 ` [Bug tree-optimization/109175] " pinskia at gcc dot gnu.org 2023-03-24 18:20 ` malat at debian dot org 2023-03-24 18:46 ` pinskia at gcc dot gnu.org [this message] 2023-03-24 19:44 ` jan.wassenberg at gmail dot com 2023-09-26 11:59 ` malat at debian dot 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-109175-4-03tfnKKOSA@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).