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 rtl-optimization/15289] [3.4/4.0 Regression] reload error with non-lowpart subregs
Date: Wed, 01 Dec 2004 18:14:00 -0000 [thread overview]
Message-ID: <20041201181407.8550.qmail@sourceware.org> (raw)
In-Reply-To: <20040505053304.15289.amodra@bigpond.net.au>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2004-12-01 18:14 -------
Subject: Bug 15289
CVSROOT: /cvs/gcc
Module name: gcc
Changes by: rth@gcc.gnu.org 2004-12-01 18:13:36
Modified files:
gcc : ChangeLog emit-rtl.c expmed.c expr.c function.c
rtl.h
Log message:
PR rtl-opt/15289
* emit-rtl.c (gen_complex_constant_part): Remove.
(gen_realpart, gen_imagpart): Remove.
* rtl.h (gen_realpart, gen_imagpart): Remove.
* expmed.c (extract_bit_field): Remove CONCAT hack catering to
gen_realpart/gen_imagpart.
* expr.c (write_complex_part, read_complex_part): New.
(emit_move_via_alt_mode, emit_move_via_integer, emit_move_resolve_push,
emit_move_complex_push, emit_move_complex, emit_move_ccmode,
emit_move_multi_word): Split out from ...
(emit_move_insn_1): ... here.
(expand_expr_real_1) <COMPLEX_EXPR>: Use write_complex_part.
<REALPART_EXPR, IMAGPART_EXPR>: Use read_complex_part.
* function.c (assign_parm_setup_reg): Hard-code transformations
instead of using gen_realpart/gen_imagpart.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.6662&r2=2.6663
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/emit-rtl.c.diff?cvsroot=gcc&r1=1.429&r2=1.430
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/expmed.c.diff?cvsroot=gcc&r1=1.210&r2=1.211
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/expr.c.diff?cvsroot=gcc&r1=1.749&r2=1.750
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/function.c.diff?cvsroot=gcc&r1=1.591&r2=1.592
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/rtl.h.diff?cvsroot=gcc&r1=1.528&r2=1.529
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15289
next prev parent reply other threads:[~2004-12-01 18:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 5:33 [Bug target/15289] New: reload error with big-endian subregs amodra at bigpond dot net dot au
2004-05-05 6:30 ` [Bug target/15289] " pinskia at gcc dot gnu dot org
2004-05-05 14:24 ` amodra at bigpond dot net dot au
2004-05-27 21:47 ` [Bug rtl-optimization/15289] reload error with non-lowpart subregs amodra at bigpond dot net dot au
2004-06-16 22:03 ` [Bug rtl-optimization/15289] [3.4/3.5 Regression] " pinskia at gcc dot gnu dot org
2004-08-19 20:53 ` mmitchel at gcc dot gnu dot org
2004-08-26 12:19 ` hubicka at gcc dot gnu dot org
2004-08-29 19:02 ` mmitchel at gcc dot gnu dot org
2004-10-31 2:08 ` [Bug rtl-optimization/15289] [3.4/4.0 " mmitchel at gcc dot gnu dot org
2004-11-28 13:08 ` steven at gcc dot gnu dot org
2004-11-28 13:27 ` amodra at bigpond dot net dot au
2004-11-28 17:54 ` giovannibajo at libero dot it
2004-11-29 21:25 ` rth at gcc dot gnu dot org
2004-12-01 18:14 ` cvs-commit at gcc dot gnu dot org [this message]
2004-12-01 18:16 ` cvs-commit at gcc dot gnu dot org
2004-12-02 19:16 ` cvs-commit at gcc dot gnu dot org
2004-12-03 23:26 ` rth at gcc dot gnu dot org
2004-12-05 5:21 ` cvs-commit at gcc dot gnu dot org
2004-12-05 5:22 ` rth at gcc dot gnu dot org
2004-12-05 5:38 ` pinskia at gcc dot gnu dot 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=20041201181407.8550.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).