public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/10404] [PPC] gcc does not use 0 when using the indexed instructions of altivec like stewx
Date: Fri, 17 Oct 2003 21:15:00 -0000 [thread overview]
Message-ID: <20031017210322.26336.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030414205600.10404.pinskia@gcc.gnu.org>
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10404
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From pinskia at gcc dot gnu dot org 2003-10-17 21:03 -------
Fixed by:
+2003-10-17 Segher Boessenkool <boessen@de.ibm.com>
+ Hartmut Penner <hpenner@de.ibm.com>
+
+ PR 10404, partial 11591, partial 11601
+ * config/rs6000/altivec.md ("altivec_dst", "altivec_dstt",
+ "altivec_dstst", "altivec_dststt", "altivec_lvsl", "altivec_lvsr",
+ "altivec_lvebx", "altivec_lvehx", "altivec_lvewx", "altivec_lvxl",
+ "altivec_lvx", "altivec_stvx", "altivec_stvxl", "altivec_stvebx",
+ "altivec_stvehx", "altivec_stvewx"): Use a memory_operand.
+ * config/rs6000/rs6000.c (altivec_expand_lv_builtin): New function.
+ (altivec_expand_stv_builtin): Adjust for the memory_operand.
+ (altivec_expand_builtin): Call altivec_expand_lv_builtin.
+ (altivec_init_builtins): Use `long int' for memory offsets.
next parent reply other threads:[~2003-10-17 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030414205600.10404.pinskia@gcc.gnu.org>
2003-10-17 21:15 ` pinskia at gcc dot gnu dot org [this message]
2003-12-04 9:44 ` pinskia at gcc dot gnu dot org
2004-01-22 7:17 ` cvs-commit at gcc dot gnu dot org
[not found] <20030414205600.10404.pinskia@physics.uc.edu>
2003-05-24 16:39 ` pinskia@physics.uc.edu
2003-06-18 5:51 ` pinskia at physics dot uc dot edu
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=20031017210322.26336.qmail@sources.redhat.com \
--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).