public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18576] New: missing jump threading because of type changes
Date: Sat, 20 Nov 2004 06:29:00 -0000	[thread overview]
Message-ID: <20041120062915.18576.pinskia@gcc.gnu.org> (raw)

struct loop
{
  int depth;
  struct loop **pred;
};

static __inline__ unsigned char
flow_loop_nested_p (const struct loop *outer, const struct loop *loop)
{
  return (loop->depth > outer->depth
  && loop->pred[outer->depth] == outer);
}

unsigned char
flow_bb_inside_loop_p (const struct loop *loop, const struct loop *source_loop)
{
  return loop == source_loop || flow_loop_nested_p (loop, source_loop);
}

In .64.final_cleanup:
<L2>:;
  iftmp.0 = 1;
  goto <bb 5> (<L14>);

<L4>:;
  iftmp.0 = 0;

<L14>:;
  if ((unsigned char) (int) (unsigned char) iftmp.0 != 0) goto <L8>; else goto <L7>;

See miss this jump threading (in fact we miss it on the RTL level also).
We do get better code already on the tree-cleanup-branch but that is because of my rewrite of PHI-OPT
for that branch we get:
<L12>:;
  iftmp.0 = 0;
  goto <bb 5> (<L4>);

<L1>:;
  iftmp.0 = (int) !(loop != *(source_loop->pred + (struct loop * *) ((unsigned int) D.1160 * 4)));

<L4>:;
  iftmp.1 = (int) ((unsigned char) (int) (unsigned char) iftmp.0 != 0);

-- 
           Summary: missing jump threading because of type changes
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P2
         Component: tree-optimization
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: pinskia at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-11-20  6:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-20  6:29 pinskia at gcc dot gnu dot org [this message]
2004-11-20  6:37 ` [Bug tree-optimization/18576] " pinskia at gcc dot gnu dot org
2004-11-20  6:43 ` pinskia at gcc dot gnu dot org
2004-11-20 16:44 ` steven at gcc dot gnu dot org
2004-11-20 17:01 ` steven at gcc dot gnu dot org
2004-11-20 17:11 ` steven at gcc dot gnu dot org
2004-11-20 17:11 ` pinskia at gcc dot gnu dot org
2004-11-20 17:57 ` [Bug tree-optimization/18576] [3.4/4.0 Regression] " pinskia at gcc dot gnu dot org
2004-11-24 22:38 ` steven at gcc dot gnu dot org
2004-11-25  0:22 ` law at redhat dot com
2004-12-12 17:26 ` kazu at cs dot umass dot edu
2004-12-12 17:42 ` kazu at cs dot umass dot edu
2004-12-13 16:33 ` law at redhat dot com
2004-12-13 17:13 ` kazu at cs dot umass dot edu
2004-12-13 17:28 ` law at redhat dot com
2004-12-22 14:08 ` kazu at cs dot umass dot edu
2005-01-06 14:43 ` tobi at gcc dot gnu dot org
2005-03-22 19:26 ` pinskia at gcc dot gnu dot org
2005-05-19 17:38 ` mmitchel at gcc dot gnu dot org
2005-07-22 21:12 ` pinskia at gcc dot gnu dot org
2005-09-27 16:17 ` mmitchel 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=20041120062915.18576.pinskia@gcc.gnu.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).