public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105232] [11 Regression] ICE in tree_to_poly_int64 via check_builtin Date: Tue, 12 Apr 2022 10:49:24 +0000 [thread overview] Message-ID: <bug-105232-4-eBWAuUR6T3@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105232-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105232 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-11 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:008d568ac7eba4057172c52d306e09d174041c59 commit r11-9813-g008d568ac7eba4057172c52d306e09d174041c59 Author: Richard Biener <rguenther@suse.de> Date: Tue Apr 12 09:54:32 2022 +0200 tree-optimization/105232 - handle overly large sizes in component_ref_size The following properly checks tree_fits_poly_int64_p before converting a size to a poly_int64. 2022-04-12 Richard Biener <rguenther@suse.de> PR tree-optimization/105232 * tree.c (component_ref_size): Bail out for too large or non-constant sizes. (cherry picked from commit 1bd96873cf73c4f59de48e9bc0d17a498f1ede04)
next prev parent reply other threads:[~2022-04-12 10:49 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-11 20:28 [Bug c/105232] New: ICE in tree_to_poly_int64, at tree.cc:3224 k.even-mendoza at imperial dot ac.uk 2022-04-11 20:43 ` [Bug tree-optimization/105232] [11/12 Regression] ICE in tree_to_poly_int64 via check_builtin pinskia at gcc dot gnu.org 2022-04-12 7:51 ` marxin at gcc dot gnu.org 2022-04-12 7:54 ` rguenth at gcc dot gnu.org 2022-04-12 7:54 ` rguenth at gcc dot gnu.org 2022-04-12 8:54 ` cvs-commit at gcc dot gnu.org 2022-04-12 8:54 ` [Bug tree-optimization/105232] [11 " rguenth at gcc dot gnu.org 2022-04-12 10:49 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-12 10:50 ` rguenth 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-105232-4-eBWAuUR6T3@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).