public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/49483] unable to vectorize code equivalent to "scalbnf"
Date: Tue, 21 Jun 2011 10:51:00 -0000	[thread overview]
Message-ID: <bug-49483-4-oMKAvkr0vO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49483-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> 2011-06-21 10:50:14 UTC ---
On Tue, 21 Jun 2011, vincenzo.innocente at cern dot ch wrote:

> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49483
> 
> --- Comment #2 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2011-06-21 10:42:01 UTC ---
> great!
> 
> unfortunately
> gcc-4.7-20110528 $ patch -p0 < vect.patch 
> patching file gcc/tree-vect-stmts.c
> Hunk #1 FAILED at 2089.
> Hunk #2 FAILED at 2099.
> Hunk #3 FAILED at 2134.
> 3 out of 3 hunks FAILED -- saving rejects to file gcc/tree-vect-stmts.c.rej
> 
> so I edit gcc/tree-vect-stmts.c by hand 
> and worked!
> 
> vldexpf.cc:16: note: LOOP VECTORIZED.
> 
> hope it will make it for 4.6.1 :-)

Unlikely unless it is a regression ;)  It'll make 4.7.0 though if
testing succeeds.

Richard.


  parent reply	other threads:[~2011-06-21 10:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-21  9:04 [Bug tree-optimization/49483] New: " vincenzo.innocente at cern dot ch
2011-06-21  9:27 ` [Bug tree-optimization/49483] " rguenth at gcc dot gnu.org
2011-06-21 10:42 ` vincenzo.innocente at cern dot ch
2011-06-21 10:51 ` rguenther at suse dot de [this message]
2011-06-21 11:03 ` rguenth at gcc dot gnu.org
2011-06-21 11:04 ` 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=bug-49483-4-oMKAvkr0vO@http.gcc.gnu.org/bugzilla/ \
    --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).