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 c++/106654] [C++23] P1774 - Portable assumptions Date: Thu, 20 Oct 2022 00:37:38 +0000 [thread overview] Message-ID: <bug-106654-4-beWbEHGryC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106654-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106654 --- Comment #17 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:53e6d7a3102409f0f2a5a9ffbfbeaa62c135d991 commit r13-3394-g53e6d7a3102409f0f2a5a9ffbfbeaa62c135d991 Author: Andrew MacLeod <amacleod@redhat.com> Date: Tue Oct 18 16:29:49 2022 -0400 Add assume support to VRP. This provides an assume_query class using rangers GORI module to determine what ranges would be applied to any SSA NAMES in the function if the return value were [1, 1]. Any parameter ranges are stored in the SSA_NAME_RANGE_INFO field, and ranger's inferred range machinery is then used to look these up and match them to assume call parameteres in the bodies of other functions.. PR c++/106654 gcc/ * gimple-range-gori.h (compute_operand_range): Make public. * gimple-range-infer.cc (gimple_infer_range::check_assume_func): New. (gimple_infer_range::gimple_infer_range): Check for assume calls. * gimple-range-infer.h (check_assume_func): Add prototype. * gimple-range.cc (assume_query::assume_range_p): New. (assume_query::range_of_expr): New. (assume_query::assume_query): New. (assume_query::calculate_op): New. (assume_query::calculate_phi): New. (assume_query::check_taken_edge): New. (assume_query::calculate_stmt): New. (assume_query::dump): New. * gimple-range.h (class assume_query): New. * tree-vrp.cc (pass_assumptions::execute): Add processing. gcc/testsuite/ * g++.dg/cpp23/attr-assume-opt.C: New.
next prev parent reply other threads:[~2022-10-20 0:37 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-16 17:20 [Bug c++/106654] New: " mpolacek at gcc dot gnu.org 2022-09-14 9:52 ` [Bug c++/106654] " jakub at gcc dot gnu.org 2022-09-14 11:23 ` rguenth at gcc dot gnu.org 2022-09-14 11:26 ` rguenth at gcc dot gnu.org 2022-09-14 11:54 ` jakub at gcc dot gnu.org 2022-09-16 9:20 ` pilarlatiesa at gmail dot com 2022-09-16 16:48 ` jakub at gcc dot gnu.org 2022-09-17 11:34 ` aldyh at gcc dot gnu.org 2022-09-17 12:09 ` jason at gcc dot gnu.org 2022-09-17 12:12 ` aldyh at gcc dot gnu.org 2022-09-17 12:29 ` jason at gcc dot gnu.org 2022-09-17 18:32 ` aldyh at gcc dot gnu.org 2022-09-21 17:49 ` jakub at gcc dot gnu.org 2022-10-06 7:01 ` cvs-commit at gcc dot gnu.org 2022-10-07 14:20 ` jakub at gcc dot gnu.org 2022-10-08 10:45 ` jakub at gcc dot gnu.org 2022-10-18 8:40 ` cvs-commit at gcc dot gnu.org 2022-10-20 0:37 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-20 19:43 ` cvs-commit at gcc dot gnu.org 2022-11-19 9:24 ` jakub at gcc dot gnu.org 2022-11-28 22:32 ` pinskia 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-106654-4-beWbEHGryC@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).