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/111303] [14 Regression] ICE: in type, at value-range.h:869 Date: Mon, 18 Sep 2023 02:19:07 +0000 [thread overview] Message-ID: <bug-111303-4-V1H7j5V5bd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111303-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111303 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jiu Fu Guo <guojiufu@gcc.gnu.org>: https://gcc.gnu.org/g:55b22a6f630e76a0be913ced8bf1b017eaffd89b commit r14-4082-g55b22a6f630e76a0be913ced8bf1b017eaffd89b Author: Jiufu Guo <guojiufu@linux.ibm.com> Date: Wed Sep 13 16:12:05 2023 +0800 use local range for one more pattern in match.pd For "get_global_range_query" SSA_NAME_RANGE_INFO can be queried. For "get_range_query", it could get more context-aware range info. And look at the implementation of "get_range_query", it returns global range if no local fun info. ATTRIBUTE_RETURNS_NONNULL inline range_query * get_range_query (const struct function *fun) { return (fun && fun->x_range_query) ? fun->x_range_query : &global_ranges; } So, using "get_range_query" would cover more case. For example, the test case of "pr111303.c". PR middle-end/111303 gcc/ChangeLog: * match.pd ((t * 2) / 2): Update pattern. gcc/testsuite/ChangeLog: * gcc.dg/tree-ssa/pr111303.c: New test.
next prev parent reply other threads:[~2023-09-18 2:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-06 8:24 [Bug c/111303] New: " shaohua.li at inf dot ethz.ch 2023-09-06 9:21 ` [Bug c/111303] " shaohua.li at inf dot ethz.ch 2023-09-06 11:12 ` guojiufu at gcc dot gnu.org 2023-09-06 11:13 ` guojiufu at gcc dot gnu.org 2023-09-06 12:36 ` guojiufu at gcc dot gnu.org 2023-09-06 12:47 ` guojiufu at gcc dot gnu.org 2023-09-06 22:52 ` [Bug tree-optimization/111303] [14 Regression] " pinskia at gcc dot gnu.org 2023-09-09 16:03 ` pinskia at gcc dot gnu.org 2023-09-09 16:04 ` pinskia at gcc dot gnu.org 2023-09-13 1:32 ` cvs-commit at gcc dot gnu.org 2023-09-18 2:19 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-18 2:31 ` guojiufu at gcc dot gnu.org 2023-09-18 2:38 ` guojiufu 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-111303-4-V1H7j5V5bd@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).