public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/20514] New: hoisting of label out of jumptable would take place at cse, should happen at trees
Date: Thu, 17 Mar 2005 08:21:00 -0000	[thread overview]
Message-ID: <20050317082132.20514.aoliva@gcc.gnu.org> (raw)

The following testcase from bug 18628 exposes a case in which cse would have
folded a load from a jump table into a label.  Jeff suspects this should have
happened earlier, in the tree level, so he asked me to file this bug.  Here's
the testcase:

int i;
int main()
{
  for (;;)
  {
    switch (i)
    {
      case 0:
      case 1:
        return 1;

      case 2:
      case 3:
        return 0;

      case 5:
        --i;
    }
  }
}

-- 
           Summary: hoisting of label out of jumptable would take place at
                    cse, should happen at trees
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: tree-optimization
        AssignedTo: law at gcc dot gnu dot org
        ReportedBy: aoliva at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
OtherBugsDependingO 19721
             nThis:


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


             reply	other threads:[~2005-03-17  8:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17  8:21 aoliva at gcc dot gnu dot org [this message]
2005-03-17 17:23 ` [Bug tree-optimization/20514] " pinskia at gcc dot gnu dot org
2005-04-13 18:30 ` pinskia at gcc dot gnu dot org
2005-05-06  8:50 ` steven at gcc dot gnu dot org
2005-05-06 13:40 ` pinskia 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=20050317082132.20514.aoliva@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).