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/21723] [4.0 Regression] ICE while building libgfortran
Date: Wed, 03 Aug 2005 16:39:00 -0000 [thread overview]
Message-ID: <20050803163915.17691.qmail@sourceware.org> (raw)
In-Reply-To: <20050523171154.21723.mgalgoci@redhat.com>
------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-08-03 16:39 -------
Subject: Bug 21723
CVSROOT: /cvs/gcc
Module name: gcc
Branch: gcc-3_4-branch
Changes by: danglin@gcc.gnu.org 2005-08-03 16:39:02
Modified files:
gcc : ChangeLog
gcc/config/pa : pa.md pa32-regs.h pa64-regs.h
Log message:
PR target/21723
* pa.md: Remove fcpy alternative from movhi and movqi patterns.
* pa32-regs.h (HARD_REGNO_NREGS): Return two floating point registers
for complex modes when generating code for PA 1.0.
(VALID_FP_MODE_P): New macro.
(HARD_REGNO_MODE_OK): Use VALID_FP_MODE_P. Use non-overlapping register
sets for all general and floating point modes. Align wide floating
point modes to even register boundaries to comply with architectural
requirements.
(CLASS_MAX_NREGS): Update to align with change to HARD_REGNO_NREGS.
* pa64-regs.h (HARD_REGNO_NREGS): Update comment and formatting.
(VALID_FP_MODE_P): New macro.
(HARD_REGNO_MODE_OK): Use VALID_FP_MODE_P. Use non-overlapping register
sets for all general and floating point modes. Align wide floating
point modes to even register boundaries to comply with architectural
requirements.
Patches:
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=2.2326.2.895&r2=2.2326.2.896
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/pa/pa.md.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.138.4.9&r2=1.138.4.10
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/pa/pa32-regs.h.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.12&r2=1.12.20.1
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/config/pa/pa64-regs.h.diff?cvsroot=gcc&only_with_tag=gcc-3_4-branch&r1=1.13.10.1&r2=1.13.10.2
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21723
prev parent reply other threads:[~2005-08-03 16:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-23 17:12 [Bug fortran/21723] New: ICE while building gfortran mgalgoci at redhat dot com
2005-05-23 17:13 ` [Bug fortran/21723] " mgalgoci at redhat dot com
2005-05-23 17:14 ` mgalgoci at redhat dot com
2005-05-23 17:15 ` [Bug target/21723] ICE while building libgfortran pinskia at gcc dot gnu dot org
2005-05-23 17:21 ` [Bug c/21723] " mgalgoci at redhat dot com
2005-05-23 17:22 ` [Bug target/21723] " mgalgoci at redhat dot com
2005-05-23 17:50 ` pinskia at gcc dot gnu dot org
2005-05-23 17:59 ` [Bug target/21723] [4.0/4.1 Regression] " pinskia at gcc dot gnu dot org
2005-06-30 17:34 ` pinskia at gcc dot gnu dot org
2005-07-02 2:52 ` danglin at gcc dot gnu dot org
2005-07-02 2:58 ` danglin at gcc dot gnu dot org
2005-07-05 1:57 ` cvs-commit at gcc dot gnu dot org
2005-07-05 2:21 ` danglin at gcc dot gnu dot org
2005-07-25 15:53 ` [Bug target/21723] [4.0 " pinskia at gcc dot gnu dot org
2005-07-29 15:27 ` cvs-commit at gcc dot gnu dot org
2005-07-31 0:46 ` pinskia at gcc dot gnu dot org
2005-08-03 16:39 ` cvs-commit at gcc dot gnu dot org [this message]
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=20050803163915.17691.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).