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/48739] [4.5/4.6/4.7 Regression] ICE in check_loop_closed_ssa_use() with "-ftree-parallelize-loops=2 -fno-tree-dominator-opts"
Date: Fri, 19 Aug 2011 23:05:00 -0000	[thread overview]
Message-ID: <bug-48739-4-9movFJYLJb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48739-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48739

--- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-08-19 23:04:36 UTC ---
(In reply to comment #1)
> Simplified testcase:
> 
> /* PR tree-optimization/48739 */
> /* { dg-do compile } */
> /* { dg-options "-O1 -ftree-parallelize-loops=2 -fno-tree-dominator-opts" } */
> 
> extern int g;
> extern void bar (void);
> 
> int
> foo (int x)
> {
>   int a, b, *c = (int *) 0;
>   for (a = 0; a < 10; ++a)
>     {
>       bar ();
>       for (b = 0; b < 5; ++b)
>         {
>           x = 0;
>           c = &x;
>           g = 1;
>         }
>     }
>   *c = x;
>   for (x = 0; x != 10; x++)
>     ;
>   return g;
> }
> 
> Started with http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=149206
> (before that the empty loop would be just removed).
> 
> The bug seems to be that parloops pass requests TODO_rebuild_alias which
> changes x from TREE_ADDRESSABLE to a gimple var, but we are in loop closed SSA
> form at that point and nothing ensures that the optimized variable is put into
> loop closed SSA form.

The bug would be that TODO_rebuild_alias does a TODO_update_address_taken.
But really parloops should be re-architected to not require a
TODO_rebuild_alias ... (it isn't required anymore for correctness anyway)


  parent reply	other threads:[~2011-08-19 23:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23  7:36 [Bug tree-optimization/48739] New: " arthur.j.odwyer at gmail dot com
2011-08-19 16:43 ` [Bug tree-optimization/48739] [4.5/4.6/4.7 Regression] " jakub at gcc dot gnu.org
2011-08-19 16:58 ` jakub at gcc dot gnu.org
2011-08-19 18:04 ` jakub at gcc dot gnu.org
2011-08-19 23:05 ` rguenth at gcc dot gnu.org [this message]
2011-08-20  7:51 ` jakub at gcc dot gnu.org
2011-08-20  7:58 ` jakub at gcc dot gnu.org
2011-08-20  8:32 ` [Bug tree-optimization/48739] [4.5 " jakub at gcc dot gnu.org
2012-06-20 12:59 ` rguenth at gcc dot gnu.org
2012-07-02  9:51 ` 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-48739-4-9movFJYLJb@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).