This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/15718] [3.3 regression][alpha] ICE in subreg_hard_regno, at emit-rtl.c:928
- From: "jbuck at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Jun 2004 01:03:03 -0000
- Subject: [Bug target/15718] [3.3 regression][alpha] ICE in subreg_hard_regno, at emit-rtl.c:928
- References: <20040528234440.15718.jbuck@gcc.gnu.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From jbuck at gcc dot gnu dot org 2004-06-02 01:03 -------
OK, I'll reluctantly accept leaving this as WONTFIX if people can help me
produce a release note saying how to avoid the bug.
"Avoid passing __complex__ in a register" doesn't cut it, because the user
doesn't write "__complex__" or "register".
Consider g77.f-torture/execute/19990826-2.f . In this case we have a simple
Fortran program that defines an inline function with a complex argument.
Evidently we have to tell Fortran users that they must never do this?
In short: what are the contexts in which a __complex__ is passed in a register
on the Alpha? Are all such contexts broken?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15718