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/107986] [12/13/14 Regression] Bogus -Warray-bounds diagnostic with std::sort Date: Wed, 24 May 2023 21:19:11 +0000 [thread overview] Message-ID: <bug-107986-4-ocY9tKvLT6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107986-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107986 --- Comment #9 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:1cd5bc387c453126fdb4c9400096180484ecddee commit r14-1179-g1cd5bc387c453126fdb4c9400096180484ecddee Author: Andrew MacLeod <amacleod@redhat.com> Date: Wed May 24 09:52:26 2023 -0400 Gimple range PHI analyzer and testcases Provide a PHI analyzer framework to provive better initial values for PHI nodes which formk groups with initial values and single statements which modify the PHI values in some predicatable way. PR tree-optimization/107822 PR tree-optimization/107986 gcc/ * Makefile.in (OBJS): Add gimple-range-phi.o. * gimple-range-cache.h (ranger_cache::m_estimate): New phi_analyzer pointer member. * gimple-range-fold.cc (fold_using_range::range_of_phi): Use phi_analyzer if no loop info is available. * gimple-range-phi.cc: New file. * gimple-range-phi.h: New file. * tree-vrp.cc (execute_ranger_vrp): Utililze a phi_analyzer. gcc/testsuite/ * gcc.dg/pr107822.c: New. * gcc.dg/pr107986-1.c: New.
next prev parent reply other threads:[~2023-05-24 21:19 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-06 7:28 [Bug tree-optimization/107986] New: [12/13 " rguenth at gcc dot gnu.org 2022-12-06 7:28 ` [Bug tree-optimization/107986] " rguenth at gcc dot gnu.org 2022-12-06 7:43 ` rguenth at gcc dot gnu.org 2022-12-06 7:51 ` pinskia at gcc dot gnu.org 2022-12-06 7:53 ` rguenth at gcc dot gnu.org 2022-12-06 7:55 ` rguenth at gcc dot gnu.org 2022-12-06 9:38 ` jakub at gcc dot gnu.org 2022-12-06 9:47 ` rguenther at suse dot de 2022-12-06 9:54 ` rguenth at gcc dot gnu.org 2022-12-07 17:12 ` amacleod at redhat dot com 2023-05-08 12:26 ` [Bug tree-optimization/107986] [12/13/14 " rguenth at gcc dot gnu.org 2023-05-24 21:19 ` cvs-commit at gcc dot gnu.org [this message] 2023-09-28 7:45 ` asharafutdinov at adalisk dot com 2023-12-15 13:45 ` rguenth at gcc dot gnu.org 2024-06-03 18:26 ` [Bug tree-optimization/107986] [12/13/14/15 " teodor_spaeren at riseup dot net 2024-06-20 9:11 ` 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-107986-4-ocY9tKvLT6@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).