public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/113012] [13/14 regression] ICE when building xorg-server with -fsanitize=undefined Date: Thu, 14 Dec 2023 14:07:04 +0000 [thread overview] Message-ID: <bug-113012-4-16B09N6myo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113012-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113012 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Obviously we shouldn't ICE on this. But, saying 0 as usable size on such UB pointer is I think completely valid (making it clear that you can't really dereference such pointer nor anything derived from it, even *++widths is invalid), just obviously it can't appear as lhs of assignment...
next prev parent reply other threads:[~2023-12-14 14:07 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-14 2:29 [Bug middle-end/113012] New: [14 " sjames at gcc dot gnu.org 2023-12-14 2:33 ` [Bug tree-optimization/113012] " pinskia at gcc dot gnu.org 2023-12-14 3:00 ` [Bug tree-optimization/113012] [13/14 " pinskia at gcc dot gnu.org 2023-12-14 3:02 ` pinskia at gcc dot gnu.org 2023-12-14 3:03 ` pinskia at gcc dot gnu.org 2023-12-14 3:14 ` [Bug sanitizer/113012] " pinskia at gcc dot gnu.org 2023-12-14 12:53 ` jakub at gcc dot gnu.org 2023-12-14 13:59 ` rguenth at gcc dot gnu.org 2023-12-14 14:00 ` rguenth at gcc dot gnu.org 2023-12-14 14:07 ` jakub at gcc dot gnu.org [this message] 2023-12-14 14:20 ` jakub at gcc dot gnu.org 2023-12-20 0:29 ` [Bug tree-optimization/113012] " cvs-commit at gcc dot gnu.org 2024-01-09 15:55 ` [Bug tree-optimization/113012] [13 " jakub at gcc dot gnu.org 2024-01-09 15:59 ` siddhesh at gcc dot gnu.org 2024-01-11 17:14 ` cvs-commit at gcc dot gnu.org 2024-01-11 17:14 ` siddhesh 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-113012-4-16B09N6myo@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).