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/109716] mesa/r300 bogus stringop-overread "reading 4 bytes from a region of size 0" Date: Thu, 04 May 2023 19:10:14 +0000 [thread overview] Message-ID: <bug-109716-4-7fDDrUSdvH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109716-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109716 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- The warning comes from: <bb 24> [local count: 64057779]: util_format_unswizzle_4f (&border_swizzled, _42, 64B); goto <bb 38>; [100.00%] Jump threading and having util_format_description declared as const causes a null pointer for desc to prograted into the argument of that function. Some places check the return value of util_format_description to see if it was non-null whiles others do not. I am not sure if we can assert the return value of util_format_description is non-null in r300_get_border_color but that removes the warning. That is: static uint32_t r300_get_border_color(enum pipe_format format, const float border[4], boolean is_r500) { const struct util_format_description *desc; float border_swizzled[4] = {0}; union util_color uc = {0}; desc = util_format_description(format); if (desc == 0) __builtin_unreachable();
prev parent reply other threads:[~2023-05-04 19:10 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-03 14:36 [Bug c/109716] New: " david at ixit dot cz 2023-05-03 18:09 ` [Bug tree-optimization/109716] " pinskia at gcc dot gnu.org 2023-05-04 18:42 ` david at ixit dot cz 2023-05-04 18:47 ` [Bug tree-optimization/109716] mesa/r300 " pinskia at gcc dot gnu.org 2023-05-04 19:10 ` pinskia at gcc dot gnu.org [this message]
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-109716-4-7fDDrUSdvH@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).