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 rtl-optimization/97554] ICE: during RTL pass: cprop /segfault in sbitmap Date: Tue, 01 Dec 2020 11:02:40 +0000 [thread overview] Message-ID: <bug-97554-4-ri4yRciepL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97554-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97554 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-8 branch has been updated by Richard Biener <rguenth@gcc.gnu.org>: https://gcc.gnu.org/g:46384dc73076d945c9222b3f0850a9aa3e694eda commit r8-10657-g46384dc73076d945c9222b3f0850a9aa3e694eda Author: Richard Biener <rguenther@suse.de> Date: Mon Oct 26 10:10:46 2020 +0100 middle-end/97554 - avoid overflow in alloc size compute This avoids overflow in the allocation size computations in sbitmap_vector_alloc when the result exceeds 2GB. 2020-10-26 Richard Biener <rguenther@suse.de> PR middle-end/97554 * sbitmap.c (sbitmap_vector_alloc): Use size_t for byte quantities to avoid overflow. (cherry picked from commit 50f9e1f4d458e36d306b2449c689e45492847f68)
next prev parent reply other threads:[~2020-12-01 11:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-23 16:34 [Bug rtl-optimization/97554] New: " rimvydas.jas at gmail dot com 2020-10-26 8:05 ` [Bug rtl-optimization/97554] " rguenth at gcc dot gnu.org 2020-10-26 10:34 ` rguenth at gcc dot gnu.org 2020-10-26 17:13 ` rimvydas.jas at gmail dot com 2020-12-01 10:12 ` rguenth at gcc dot gnu.org 2020-12-01 10:13 ` rguenth at gcc dot gnu.org 2020-12-01 10:32 ` cvs-commit at gcc dot gnu.org 2020-12-01 10:50 ` cvs-commit at gcc dot gnu.org 2020-12-01 11:02 ` cvs-commit at gcc dot gnu.org [this message] 2020-12-01 11:03 ` 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-97554-4-ri4yRciepL@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).