public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Jan Hubicka <hubicka@ucw.cz>
Cc: gcc-patches@gcc.gnu.org, rguenther@suse.de, jason@redhat.com
Subject: Re: Teach vrp that THIS pointer and references are non-zero
Date: Mon, 13 Apr 2015 10:22:00 -0000	[thread overview]
Message-ID: <20150413102242.GK1735@tucnak.redhat.com> (raw)
In-Reply-To: <20150413101249.GB61490@kam.mff.cuni.cz>

On Mon, Apr 13, 2015 at 12:12:49PM +0200, Jan Hubicka wrote:
> @@ -1216,6 +1227,10 @@ gimple_stmt_nonzero_warnv_p (gimple stmt
>  	    && DECL_IS_OPERATOR_NEW (fndecl)
>  	    && !TREE_NOTHROW (fndecl))
>  	  return true;
> +	/* Referneces are alwyas non-NULL.  */

Two typos.

I'll defer the patch review to richi/jason; as far as ubsan is concerned,
the flag_delete_null_pointer_checks guards should hopefully make sure we are
ok.

	Jakub

  reply	other threads:[~2015-04-13 10:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 10:12 Jan Hubicka
2015-04-13 10:22 ` Jakub Jelinek [this message]
2015-04-13 11:48 ` Richard Biener
2015-04-13 12:17   ` Jan Hubicka
2015-04-13 12:18     ` Richard Biener
2015-04-15 13:07       ` Jason Merrill

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=20150413102242.GK1735@tucnak.redhat.com \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=jason@redhat.com \
    --cc=rguenther@suse.de \
    /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).