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 optimization/13875] [tree-ssa] missed jump thread optimization on the tree-level
Date: Tue, 06 Apr 2004 01:44:00 -0000	[thread overview]
Message-ID: <20040406014425.22401.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040127051055.13875.dann@godzilla.ics.uci.edu>


------- Additional Comments From pinskia at gcc dot gnu dot org  2004-04-06 01:44 -------
You do not have to file a new bug, I have a fix already, the issue has to do with casts:
bool PT<GPROGRAM>::isReallyPossible() const [with GPROGRAM = GRULES] (this)
{
  TruthValue T.3218;
  int iftmp.14093;

<bb 0>:
  if (this->allowsPositive) goto <L0>; else goto <L11>;

<L0>:;
  T.3218 = *(((struct GINTERPRET *)this->I)->array + (TruthValue *)(((struct 
__normal_iterator<constGATOM*,std::vector<GATOM, std::allocator<GATOM> > > *)this + 12B)-
>_M_current->index * 4));
  if (T.3218 == 0) goto <L17>; else goto <L4>;

<L17>:;
  iftmp.14093 = 1;
  goto <bb 4> (<L10>);

<L4>:;
  if (T.3218 == 2) goto <L8>; else goto <L18>;

<L18>:;
  iftmp.14093 = 0;
  goto <bb 4> (<L10>);

<L8>:;
  iftmp.14093 = 1;

<L10>:;
  return iftmp.14093;

<L11>:;
  return (int)*(((struct GINTERPRET *)this->I)->array + (TruthValue *)(((struct GATOM *)(struct GATOM 
&)((struct __normal_iterator<constTLITERAL<GATOM>*,std::vector<TLITERAL<GATOM>, std::
allocator<TLITERAL<GATOM> > > > *)this + 16B)->_M_current)->index * 4)) == 0;

}

-- 


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


  parent reply	other threads:[~2004-04-06  1:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27  5:11 [Bug optimization/13875] New: [tree-ssa] function not optimized dann at godzilla dot ics dot uci dot edu
2004-01-27  5:13 ` [Bug optimization/13875] " pinskia at gcc dot gnu dot org
2004-01-30  0:33 ` pinskia at gcc dot gnu dot org
2004-01-31  3:43 ` pinskia at gcc dot gnu dot org
2004-02-29  4:01 ` [Bug optimization/13875] [tree-ssa] missed jump thread optimization on the tree-level pinskia at gcc dot gnu dot org
2004-02-29  4:09 ` pinskia at gcc dot gnu dot org
2004-03-01  3:43 ` law at gcc dot gnu dot org
2004-03-01 17:52 ` law at gcc dot gnu dot org
2004-03-01 19:51 ` giovannibajo at libero dot it
2004-03-03 18:14 ` dann at godzilla dot ics dot uci dot edu
2004-03-03 18:26 ` law at redhat dot com
2004-03-08  2:07 ` law at redhat dot com
2004-03-08  2:09 ` law at gcc dot gnu dot org
2004-03-08 23:47 ` dann at godzilla dot ics dot uci dot edu
2004-03-08 23:51 ` pinskia at gcc dot gnu dot org
2004-03-09 23:37 ` law at redhat dot com
2004-04-06  1:27 ` dann at godzilla dot ics dot uci dot edu
2004-04-06  1:44 ` pinskia at gcc dot gnu dot org [this message]
2004-04-08 22:58 ` law at redhat dot com
2004-04-08 23:36 ` dann at godzilla dot ics dot uci dot edu
2004-04-08 23:45 ` law at redhat dot com
2004-04-20 16:40 ` dann at godzilla dot ics dot uci dot edu
2004-05-27  7:54 ` [Bug tree-optimization/13875] " pinskia at gcc dot gnu dot org
2004-06-02 20:16 ` pinskia at gcc dot gnu dot org
2004-10-11 17:08 ` pinskia at gcc dot gnu dot org
2005-01-15  5:38 ` pinskia at gcc dot gnu dot org
2005-06-12 20:41 ` pinskia at gcc dot gnu dot org
2005-06-13 13:52 ` law at redhat dot com

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=20040406014425.22401.qmail@sources.redhat.com \
    --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).