public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Fix PR78847
Date: Thu, 09 Feb 2017 08:01:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1702090851570.6076@zhemvz.fhfr.qr> (raw)


The following patch fixes a missed optimization caused by niter analysis
returning a complex pointer subtraction expression instead of a constant
for a loop with a pointer IV (it looks like pointer IVs are quite common
in libstdc++).

Bootstrapped and tested on x86_64-unknown-linux-gnu.

Not a regression (well, didn't try to find a release where we optimized
the testcase, but it needs c++14 library support anyway).  I'm also
not quite sure associate_trees handles pointer types correctly
(there is some pointer type handling in the associate case but
POINTER_PLUS_EXPR folding for example does not dispatch to associate).

I guess trying to add some more exhaustive testcases for GENERIC input
is required.

Thanks,
Richard.

2017-02-09  Richard Biener  <rguenther@suse.de>

	PR tree-optimization/78847
	* fold-const.c (split_tree): Handle POINTER_PLUS_EXPR.

	* g++.dg/tree-ssa/pr78847.C: New testcase.

Index: gcc/fold-const.c
===================================================================
*** gcc/fold-const.c	(revision 245276)
--- gcc/fold-const.c	(working copy)
*************** split_tree (location_t loc, tree in, tre
*** 785,791 ****
  		  the value is not affected.  For reals, the value might be
  		  affected, so we can't.  */
  	       && ((code == PLUS_EXPR && TREE_CODE (in) == MINUS_EXPR)
! 		   || (code == MINUS_EXPR && TREE_CODE (in) == PLUS_EXPR))))
      {
        tree op0 = TREE_OPERAND (in, 0);
        tree op1 = TREE_OPERAND (in, 1);
--- 785,793 ----
  		  the value is not affected.  For reals, the value might be
  		  affected, so we can't.  */
  	       && ((code == PLUS_EXPR && TREE_CODE (in) == MINUS_EXPR)
! 		   || (code == MINUS_EXPR
! 		       && (TREE_CODE (in) == PLUS_EXPR
! 			   || TREE_CODE (in) == POINTER_PLUS_EXPR)))))
      {
        tree op0 = TREE_OPERAND (in, 0);
        tree op1 = TREE_OPERAND (in, 1);
Index: gcc/testsuite/g++.dg/tree-ssa/pr78847.C
===================================================================
*** gcc/testsuite/g++.dg/tree-ssa/pr78847.C	(nonexistent)
--- gcc/testsuite/g++.dg/tree-ssa/pr78847.C	(working copy)
***************
*** 0 ****
--- 1,26 ----
+ /* { dg-do compile } */
+ /* { dg-require-effective-target c++14 } */
+ /* { dg-options "-O3 -fdump-tree-ldist" } */
+ 
+ #include <stddef.h>
+ #include <cstring>
+ #include <experimental/string_view>
+ 
+ using string_view = std::experimental::string_view;
+ 
+ class Foo {
+     constexpr static size_t Length = 9;
+     char ascii_[Length];
+ public:
+     Foo();
+     string_view view() const {
+ 	return string_view(ascii_, Length);
+     }
+ };
+ 
+ void testWithLoopValue(const Foo foo, size_t ptr, char *buf_) {
+     for (auto c : foo.view())
+       buf_[ptr++] = c;
+ }
+ 
+ /* { dg-final { scan-tree-dump "memcpy\[^\n\r\]*, 9\\);" "ldist" } } */

             reply	other threads:[~2017-02-09  8:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-09  8:01 Richard Biener [this message]
2017-04-21 12:46 ` 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=alpine.LSU.2.20.1702090851570.6076@zhemvz.fhfr.qr \
    --to=rguenther@suse.de \
    --cc=gcc-patches@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).