[Bug target/15718] [3.3 regression][alpha] ICE in subreg_hard_regno, at emit-rtl.c:928

["gdr at integrable-solutions dot net" <gcc-bugzilla at gcc dot gnu dot org>]

------- Additional Comments From gdr at integrable-solutions dot net  2004-06-02 02:25 -------
Subject: Re:  [3.3 regression][alpha] ICE in subreg_hard_regno, at emit-rtl.c:928

"jbuck at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> writes:

| 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".

That is fully understood, but that comment was made as an explanation
of what was going on to you (Joe), much more knowledgeable than "the user"
(even if you happen to be user too, but then you're not a common user
:-))

| 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?

My understanding is that the contexts are those where you have an
equivalent of bytewise copy.  RTH may have better words to
explain that. 

-- Gaby


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15718