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/97538] [11 Regression] ICE in during GIMPLE pass: wrestrict since r11-4135-ge864d395b4e862ce Date: Sat, 24 Oct 2020 08:40:48 +0000 [thread overview] Message-ID: <bug-97538-4-KH7DQJN48C@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97538-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97538 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Aldy Hernandez <aldyh@gcc.gnu.org>: https://gcc.gnu.org/g:16e2427f50c208dfe07d07f18009969502c25dc8 commit r11-4336-g16e2427f50c208dfe07d07f18009969502c25dc8 Author: Aldy Hernandez <aldyh@redhat.com> Date: Fri Oct 23 15:54:58 2020 +0200 Handle undefined ranges in get_size_range. An undefined range was leaking through to the end of this function, which leads us to use an uninitialized wide_int. gcc/ChangeLog: PR tree-optimization/97538 * calls.c (get_size_range): Handle undefined ranges. gcc/testsuite/ChangeLog: * g++.dg/pr97538.C: New test.
next prev parent reply other threads:[~2020-10-24 8:40 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-23 7:20 [Bug tree-optimization/97538] New: ICE in during GIMPLE pass: wrestrict marxin at gcc dot gnu.org 2020-10-23 7:20 ` [Bug tree-optimization/97538] " marxin at gcc dot gnu.org 2020-10-23 9:31 ` marxin at gcc dot gnu.org 2020-10-23 9:34 ` [Bug tree-optimization/97538] ICE in during GIMPLE pass: wrestrict since r11-4135-ge864d395b4e862ce marxin at gcc dot gnu.org 2020-10-23 14:12 ` [Bug tree-optimization/97538] [11 Regression] " aldyh at gcc dot gnu.org 2020-10-24 8:40 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-24 8:41 ` aldyh 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-97538-4-KH7DQJN48C@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).