public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/36343] [4.3/4.4 Regression] Wrong code due to bad TBAA pruning of points-to-sets and use in call clobbering
Date: Tue, 27 May 2008 12:46:00 -0000	[thread overview]
Message-ID: <20080527124529.21442.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36343-10053@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from rguenth at gcc dot gnu dot org  2008-05-27 12:45 -------
If you investigate why this doesn't happen more often you find that
directly_dereferenced is only ever set if you dereference a pointer and the
result is also a pointer.  (Thus the complicated testcase)

In essence - we almost _never_ TBAA-prune the points-to-sets.

The correct solution is (apart from improving the TBAA-pruning) to use the
original points-to solution for computing the call-clobbered variables, not
the TBAA-pruned points-to set.

For 4.3 the easiest and least invasive solution is to rip out the
TBAA-pruning code completely.  This is also the temporary solution for the
mainline.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to fail|                            |4.3.0 4.4.0
      Known to work|                            |4.1.3 4.2.4
            Summary|Wrong code due to bad TBAA  |[4.3/4.4 Regression] Wrong
                   |pruning of points-to-sets   |code due to bad TBAA pruning
                   |and use in call clobbering  |of points-to-sets and use in
                   |                            |call clobbering
   Target Milestone|---                         |4.3.1


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


  parent reply	other threads:[~2008-05-27 12:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 12:42 [Bug tree-optimization/36343] New: " rguenth at gcc dot gnu dot org
2008-05-27 12:46 ` [Bug tree-optimization/36343] [4.3/4.4 Regression] " rguenth at gcc dot gnu dot org
2008-05-27 12:46 ` rguenth at gcc dot gnu dot org [this message]
2008-05-28 22:12 ` rguenth at gcc dot gnu dot org
2008-05-29 10:33 ` rguenth at gcc dot gnu dot org
2008-05-29 10:35 ` rguenth at gcc dot gnu dot org
2008-06-06 15:04 ` [Bug tree-optimization/36343] [4.3 " rguenth at gcc dot gnu dot org
2008-08-27 22:09 ` jsm28 at gcc dot gnu dot org
2008-09-17 14:47 ` rguenth at gcc dot gnu dot org
2008-09-17 15:08 ` ebotcazou at gcc dot gnu dot org
2008-09-17 15:12 ` rguenther at suse dot de
2008-09-19 15:06 ` rguenth at gcc dot gnu dot org
2008-09-19 15:07 ` rguenth at gcc dot gnu dot 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=20080527124529.21442.qmail@sourceware.org \
    --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).