public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/41082] [4.5/4.6 Regression] FAIL: gfortran.fortran-torture/execute/where_2.f90 execution,  -O3
Date: Wed, 08 Dec 2010 00:13:00 -0000	[thread overview]
Message-ID: <bug-41082-4-VWZKdAsdGj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-41082-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #63 from Jakub Jelinek <jakub at gcc dot gnu.org> 2010-12-08 00:12:52 UTC ---
Created attachment 22678
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22678
gcc46-pr41082.patch

Totally untested proof of concept patch.
The disadvantage is that as the MEM mode is not altivec-ish, it isn't forced
into reg+reg addressing early.

On the other side, when rs6000_expand_vector_extract always creates a new stack
local (shouldn't it try to share just one such slot for each mode in each
function btw?), is there any reason why a normal stvx insn can't be used
instead of these stve*x insns?  Is it a performance issue?  The difference
between stvx and stve*x I understand is just that stve*x doesn't clobber in the
memory
other bytes, while stvx stores everything in the 16 byte slot.  But we don't
care about those other bytes anyway, so if it is not a performance issue, IMHO
we should just get rid of UNSPEC_STVE stuff and store the whole vector, then
just read the bytes we want.


  parent reply	other threads:[~2010-12-08  0:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-41082-4@http.gcc.gnu.org/bugzilla/>
2010-11-22 10:06 ` [Bug middle-end/41082] " dominiq at lps dot ens.fr
2010-11-26 15:39 ` jakub at gcc dot gnu.org
2010-11-26 16:01 ` dominiq at lps dot ens.fr
2010-11-26 16:54 ` jakub at gcc dot gnu.org
2010-11-26 17:18 ` dominiq at lps dot ens.fr
2010-11-26 17:42 ` jakub at gcc dot gnu.org
2010-11-27 18:15 ` jakub at gcc dot gnu.org
2010-11-27 22:12 ` dominiq at lps dot ens.fr
2010-12-07 22:08 ` jakub at gcc dot gnu.org
2010-12-07 23:18 ` [Bug target/41082] " jakub at gcc dot gnu.org
2010-12-08  0:13 ` jakub at gcc dot gnu.org [this message]
2010-12-08  0:16 ` pinskia at gcc dot gnu.org
2010-12-08  0:33 ` jakub at gcc dot gnu.org
2010-12-08  7:36 ` jakub at gcc dot gnu.org
2010-12-08  8:29 ` jakub at gcc dot gnu.org
2010-12-08 20:30 ` meissner at gcc dot gnu.org
2010-12-09  6:15 ` dominiq at lps dot ens.fr
2010-12-09  8:34 ` jakub at gcc dot gnu.org
2010-12-09  8:36 ` [Bug target/41082] [4.5 " jakub at gcc dot gnu.org
2010-12-16 13:13 ` rguenth at gcc dot gnu.org
2011-01-16 20:13 ` jakub at gcc dot gnu.org
2011-01-17  9:14 ` jakub 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-41082-4-VWZKdAsdGj@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).