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/113013] [12/13/14 regression] ICE in fold_convert_loc with -fsanitize=undefined Date: Thu, 14 Dec 2023 03:17:11 +0000 [thread overview] Message-ID: <bug-113013-4-CaFZRz9kVl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113013-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113013 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Keywords| |ice-on-valid-code Status|UNCONFIRMED |NEW Last reconfirmed| |2023-12-14 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced slightly more: ``` struct _xPoint { short x; } xPoint; void *reallocarray() __attribute__((__alloc_size__(1))); struct _xPoint * miZeroLine_pspanInit; void miZeroLine_list_len(void) { miZeroLine_pspanInit = reallocarray(xPoint); miZeroLine_pspanInit->x = 0; } ``
next prev parent reply other threads:[~2023-12-14 3:17 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-14 3:10 [Bug tree-optimization/113013] New: " sjames at gcc dot gnu.org 2023-12-14 3:17 ` pinskia at gcc dot gnu.org [this message] 2023-12-14 3:18 ` [Bug tree-optimization/113013] " pinskia at gcc dot gnu.org 2023-12-14 3:20 ` pinskia at gcc dot gnu.org 2023-12-14 12:52 ` siddhesh at gcc dot gnu.org 2023-12-14 14:00 ` rguenth at gcc dot gnu.org 2023-12-15 13:28 ` jakub at gcc dot gnu.org 2023-12-15 13:54 ` siddhesh at gcc dot gnu.org 2023-12-18 9:00 ` cvs-commit at gcc dot gnu.org 2023-12-18 9:14 ` cvs-commit at gcc dot gnu.org 2023-12-18 9:26 ` cvs-commit at gcc dot gnu.org 2023-12-18 9:38 ` jakub 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-113013-4-CaFZRz9kVl@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).