public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dorit at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18557] Inefficient code generated by -ftree-vectorize on Alpha
Date: Fri, 19 Nov 2004 18:24:00 -0000	[thread overview]
Message-ID: <20041119182436.6518.qmail@sourceware.org> (raw)
In-Reply-To: <20041118235414.18557.falk@debian.org>


------- Additional Comments From dorit at il dot ibm dot com  2004-11-19 18:24 -------
(In reply to comment #5)
> (In reply to comment #2)
> > Subject: Re:  Inefficient code generated by
> >         -ftree-vectorize on Alpha
> > On Fri, 2004-11-19 at 00:04 +0000, pinskia at gcc dot gnu dot org wrote:
> > > ------- Additional Comments From pinskia at gcc dot gnu dot org  2004-11-
19 00:04 -------
> > > Confirmed.
> > > One issue is that we don't fold stuff:
> > >   D.1061 = 8 - 1;
> > >   D.1065 = 2 - 1;
> > 
I expect these would go away with this patch:
http://gcc.gnu.org/ml/gcc-patches/2004-11/msg01512.html



-- 


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


  parent reply	other threads:[~2004-11-19 18:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 23:54 [Bug tree-optimization/18557] New: " falk at debian dot org
2004-11-19  0:04 ` [Bug tree-optimization/18557] " pinskia at gcc dot gnu dot org
2004-11-19  3:42 ` dberlin at dberlin dot org
2004-11-19 10:50 ` giovannibajo at libero dot it
2004-11-19 11:29 ` falk at debian dot org
2004-11-19 14:21 ` pinskia at gcc dot gnu dot org
2004-11-19 18:24 ` dorit at il dot ibm dot com [this message]
2004-11-19 20:16 ` falk at debian dot org
     [not found] <bug-18557-2744@http.gcc.gnu.org/bugzilla/>
2009-02-03 12:24 ` ubizjak at gmail dot com
2009-02-03 12:25 ` ubizjak at gmail dot com
2009-02-03 12:31 ` ubizjak at gmail dot com
2009-02-03 12:51 ` falk at debian dot org
     [not found] <bug-18557-4@http.gcc.gnu.org/bugzilla/>
2012-07-13  8:54 ` rguenth at gcc dot gnu.org
2012-07-13 13:53 ` 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=20041119182436.6518.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).