public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108385] [12 Regression] false positive -Wfree-nonheap-object
Date: Fri, 13 Jan 2023 09:26:56 +0000	[thread overview]
Message-ID: <bug-108385-4-SJM0TVknl9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108385-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108385

--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
> [E]VRP testcase which shows the odd 'off' range on the false edge:
> 
> void bar(char *);
> 
> void foo (char *p, char *pp, int off)
> {
>   char *q = p + off;
>   if (q != p)
>     bar (q);
>   char *qq = pp + off;
>   if (qq != pp)
>     bar (qq);
>   bar (p);
>   bar (pp);
> }

In the old VRP code the register_edge_assert_for_* routines would be
the ones to add pattern matching for this.  I can't find where such
code exists in ranger now - I suspected it might be in range-op
when solving q = p + off; with q == p, but that operates on ranges
and not equivalences only?

  parent reply	other threads:[~2023-01-13  9:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 15:27 [Bug c++/108385] New: " steveire at gmail dot com
2023-01-12 16:39 ` [Bug tree-optimization/108385] " pinskia at gcc dot gnu.org
2023-01-12 16:44 ` pinskia at gcc dot gnu.org
2023-01-13  8:12 ` [Bug tree-optimization/108385] [12 Regression] " marxin at gcc dot gnu.org
2023-01-13  9:09 ` rguenth at gcc dot gnu.org
2023-01-13  9:13 ` rguenth at gcc dot gnu.org
2023-01-13  9:26 ` rguenth at gcc dot gnu.org [this message]
2023-01-13 20:59 ` amacleod at redhat dot com
2023-01-16  8:11 ` rguenth at gcc dot gnu.org
2023-01-31 14:58 ` cvs-commit at gcc dot gnu.org
2023-01-31 14:59 ` amacleod at redhat dot com
2023-02-01 15:02 ` amacleod at redhat dot com
2023-05-08 12:26 ` 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-108385-4-SJM0TVknl9@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: link
Be 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).