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/43965] Missed VRP and/or jump-threading
Date: Mon, 03 May 2010 09:56:00 -0000	[thread overview]
Message-ID: <20100503095551.10379.qmail@sourceware.org> (raw)
In-Reply-To: <bug-43965-19113@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from rguenth at gcc dot gnu dot org  2010-05-03 09:55 -------
Confirmed.  This is a case where we'd have to do some interesting VRP and
jump-threading.


-- 

rguenth at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
          Component|middle-end                  |tree-optimization
     Ever Confirmed|0                           |1
           Keywords|                            |missed-optimization
   Last reconfirmed|0000-00-00 00:00:00         |2010-05-03 09:55:51
               date|                            |
            Summary|doubled code (x86)          |Missed VRP and/or jump-
                   |                            |threading


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


  parent reply	other threads:[~2010-05-03  9:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03  5:45 [Bug c++/43965] New: doubled code (x86) hartmut dot schirmer at arcormail dot de
2010-05-03  5:46 ` [Bug c++/43965] " hartmut dot schirmer at arcormail dot de
2010-05-03  9:56 ` rguenth at gcc dot gnu dot org [this message]
     [not found] <bug-43965-4@http.gcc.gnu.org/bugzilla/>
2012-06-29 14:20 ` [Bug tree-optimization/43965] Missed VRP and/or jump-threading rguenth at gcc dot gnu.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=20100503095551.10379.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).