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/65506] [5 Regression] FAIL: gcc.dg/pr29215.c scan-tree-dump-not gimple "memcpy"
Date: Mon, 23 Mar 2015 09:55:00 -0000	[thread overview]
Message-ID: <bug-65506-4-GFPw6n0WLD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65506-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2015-03-23
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
   Target Milestone|---                         |5.0
     Ever confirmed|0                           |1

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Ok, that's probably caused by

2015-03-20  Richard Biener  <rguenther@suse.de>

        PR middle-end/64715
        * tree-chrec.c (chrec_fold_poly_cst): Use useless_type_conversion_p
        for type comparison and gcc_checking_assert.
        (chrec_fold_plus_poly_poly): Likewise.
        (chrec_fold_multiply_poly_poly): Likewise.
        (chrec_convert_1): Likewise.
        * gimplify.c (gimplify_expr): Remove premature folding of
        &X + CST to &MEM[&X, CST].

and should be fixed by adjusting the testcase to scan not the gimple dump
but the ccp1 dump.  Can you try that?


  reply	other threads:[~2015-03-23  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21 20:43 [Bug tree-optimization/65506] New: " danglin at gcc dot gnu.org
2015-03-23  9:55 ` rguenth at gcc dot gnu.org [this message]
2015-03-23 14:25 ` [Bug testsuite/65506] [5 Regression] " jakub at gcc dot gnu.org
2015-03-23 15:32 ` rguenth at gcc dot gnu.org
2015-03-23 15:33 ` dave.anglin at bell dot net
2015-03-23 21:32 ` jakub at gcc dot gnu.org
2015-03-23 22:29 ` jakub at gcc dot gnu.org
2015-03-24  0:10 ` olegendo at gcc dot gnu.org
2015-03-25 14:07 ` alalaw01 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-65506-4-GFPw6n0WLD@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).