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/107109] [13 Regression] ICE on valid code at -O1 on x86_64-linux-gnu: in type, at value-range.h:621 since r13-2975-g7ea258a13a115e9e Date: Mon, 03 Oct 2022 14:14:11 +0000 [thread overview] Message-ID: <bug-107109-4-bnMhM5dyed@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107109-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107109 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>: https://gcc.gnu.org/g:f41d1b39a6443fad38c36af34b1baa384954ca80 commit r13-3031-gf41d1b39a6443fad38c36af34b1baa384954ca80 Author: Andrew MacLeod <amacleod@redhat.com> Date: Sun Oct 2 18:43:35 2022 -0400 Don't process undefined range. No need to continue processing an undefined range. gcc/ PR tree-optimization/107109 * range-op.cc (adjust_op1_for_overflow): Don't process undefined. gcc/testsuite/ * gcc.dg/pr107109.c: New.
next prev parent reply other threads:[~2022-10-03 14:14 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-10-01 14:19 [Bug tree-optimization/107109] New: ICE on valid code at -O1 on x86_64-linux-gnu: in type, at value-range.h:621 zhendong.su at inf dot ethz.ch 2022-10-02 11:58 ` [Bug tree-optimization/107109] " zhendong.su at inf dot ethz.ch 2022-10-03 9:27 ` [Bug tree-optimization/107109] [13 Regression] ICE on valid code at -O1 on x86_64-linux-gnu: in type, at value-range.h:621 since r13-2975-g7ea258a13a115e9e marxin at gcc dot gnu.org 2022-10-03 14:14 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-03 14:15 ` amacleod at redhat dot com
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-107109-4-bnMhM5dyed@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).