public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: gcc-patches@gcc.gnu.org
Cc: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
	Janis Johnson <janisjo@codesourcery.com>,
	Joern Rennecke <joern.rennecke@embecosm.com>
Subject: Re: Ping: RFA: testsuite patches (1/6): keeps_null_pointer_checks effect on pta/alias dump files
Date: Thu, 05 Sep 2013 15:02:00 -0000	[thread overview]
Message-ID: <59053431-66F5-48A6-A94D-AE63CBEAF03F@comcast.net> (raw)
In-Reply-To: <20130905104227.57yizk3ick84000s-nzlynne@webmail.spamcop.net>

On Sep 5, 2013, at 7:42 AM, Joern Rennecke <joern.rennecke@embecosm.com> wrote:
> This patch has not been reviewed for more than two weeks:
> http://gcc.gnu.org/ml/gcc-patches/2013-08/msg00990.html

I'd like a pta type person (or anyone that has an opinion on the change) to review/comment on this…  Surely we have at least 1 person that still works in that area around here…

This is the type of change:

Index: gcc.dg/tree-ssa/pta-escape-2.c
===================================================================
--- gcc.dg/tree-ssa/pta-escape-2.c	(revision 201835)
+++ gcc.dg/tree-ssa/pta-escape-2.c	(working copy)
@@ -34,5 +34,5 @@ int main()
   return 0;
 }
 
-/* { dg-final { scan-tree-dump "ESCAPED = { NULL ESCAPED NONLOCAL x }" "alias" } } */
+/* { dg-final { scan-tree-dump "ESCAPED = { NULL ESCAPED NONLOCAL x }" "alias" { target { ! keeps_null_pointer_checks } } } } */
 /* { dg-final { cleanup-tree-dump "alias" } } */

if you are not sure you want to click on the link.

  reply	other threads:[~2013-09-05 15:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 14:42 Joern Rennecke
2013-09-05 15:02 ` Mike Stump [this message]
2013-09-06  6:58   ` Richard Biener
2013-09-06  9:13     ` Joern Rennecke
2013-09-06  9:21       ` Richard Biener

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=59053431-66F5-48A6-A94D-AE63CBEAF03F@comcast.net \
    --to=mikestump@comcast.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=janisjo@codesourcery.com \
    --cc=joern.rennecke@embecosm.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.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).