public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dnovillo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/14495] [tree-ssa] Propagate range info into a switch statement
Date: Fri, 03 Jun 2005 13:55:00 -0000	[thread overview]
Message-ID: <20050603135545.30936.qmail@sourceware.org> (raw)
In-Reply-To: <20040309003513.14495.kazu@cs.umass.edu>


------- Additional Comments From dnovillo at gcc dot gnu dot org  2005-06-03 13:55 -------

The issue is that the propagator engine does not implement the concept of
multiway branches taking some edges.  It supports ONE, NONE or ALL.

Frankly, I'm not at all convinced that this is worth handling.  But if we were
to handle it, the place to fix is the propagator engine.

-- 


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


  parent reply	other threads:[~2005-06-03 13:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09  0:35 [Bug optimization/14495] New: " kazu at cs dot umass dot edu
2004-03-09  0:45 ` [Bug optimization/14495] " pinskia at gcc dot gnu dot org
2004-05-24 15:57 ` [Bug tree-optimization/14495] " pinskia at gcc dot gnu dot org
2005-04-24 11:52 ` pinskia at gcc dot gnu dot org
2005-05-08 18:10 ` pinskia at gcc dot gnu dot org
2005-06-03 13:55 ` dnovillo at gcc dot gnu dot org [this message]
     [not found] <20040309003513.14495.kazu@gcc.gnu.org>
2005-09-10 18:10 ` pinskia at gcc dot gnu dot org
     [not found] <bug-14495-5009@http.gcc.gnu.org/bugzilla/>
2006-04-20 10:58 ` wouter dot vermaelen at pi dot be
2007-04-13  9:31 ` rguenth at gcc dot gnu dot org
2007-04-17 13:05 ` patchapp at dberlin dot org
2008-04-02 12:53 ` rguenth at gcc dot gnu dot org
2008-04-02 12:55 ` rguenth at gcc dot gnu dot org
2008-04-02 12:56 ` 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=20050603135545.30936.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).