public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit 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: Thu, 22 Jan 2004 07:17:00 -0000 [thread overview]
Message-ID: <20040122071747.1152.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030414205600.10404.pinskia@gcc.gnu.org>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-01-22 07:17 -------
Subject: Bug 10404
CVSROOT: /cvs/gcc
Module name: gcc
Branch: hammer-3_3-branch
Changes by: hpenner@gcc.gnu.org 2004-01-22 07:17:37
Modified files:
gcc : ChangeLog.hammer
gcc/config/rs6000: altivec.md linux64.h rs6000-protos.h rs6000.c
rs6000.h
Log message:
Backport 64 bit altivec enablement from mainline.
2004-01-08 Hartmut Penner <hpenner@de.ibm.com>
* gcc/config/rs6000/rs6000.c (easy_vector_constant): Accept
all vector constant loadable by vsplt*.
(output_vec_const_move): Likewise.
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.
2003-09-22 David Edelsohn <edelsohn@gnu.org>
Hartmut Penner <hpenner@de.ibm.com>
Segher Boessenkool <boessen@de.ibm.com>
* config/rs6000/rs6000.c (altivec_in_gprs_p): Rename to ...
(gpr_or_gpr_p): Test INT_REGNO_P and convert to boolean.
(rs6000_split_altivec_in_gprs): Rename to ...
(rs6000_split_multireg_move): Add support for update addressing.
* config/rs6000/rs6000-protos.h: Same.
* config/rs6000/altivec.md: Same.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.hammer.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.1.2.273&r2=1.1.2.274
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/rs6000/altivec.md.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.1.18.2&r2=1.1.18.3
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/rs6000/linux64.h.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.31.2.7&r2=1.31.2.8
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/rs6000/rs6000-protos.h.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.47.2.4&r2=1.47.2.5
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/rs6000/rs6000.c.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.397.2.18&r2=1.397.2.19
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/rs6000/rs6000.h.diff?cvsroot=gcc&only_with_tag=hammer-3_3-branch&r1=1.234.2.12&r2=1.234.2.13
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=10404
next prev parent reply other threads:[~2004-01-22 7:17 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
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 [this message]
[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=20040122071747.1152.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).