This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Bug 15718 dispute: showstopper or WONTFIX?
- From: Joe Buck <jbuck at welsh-buck dot org>
- To: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- Cc: Joe Buck <Joe dot Buck at synopsys dot COM>, gcc at gcc dot gnu dot org
- Date: Tue, 01 Jun 2004 21:21:03 -0700
- Subject: Re: Bug 15718 dispute: showstopper or WONTFIX?
- References: <1085810773.13920.10.camel@felicity> <m38yfbpzzt.fsf@uniton.integrable-solutions.net> <20040601181104.A23290@synopsys.com> <m38yf61xny.fsf@uniton.integrable-solutions.net>
Joe Buck <Joe.Buck@synopsys.COM> writes:
> | Since 3.3.4 shipped with this bug, we need a release note describing, in
> | user-level terms, how to avoid the bug.
> |
> | We can't write "don't pass a __complex__ in a register". After all,
On Tue, 2004-06-01 at 19:49, Gabriel Dos Reis wrote:
> Sure.
>
> Due to a calling convention bug in the Alpha backend, the compiler
> may not accept some constructs involving function calls using native
> complex numbers either as parameter values or return value.
> That undoubtedly needs polishing.
It understates the issue considerably. LAPACK 3.0 hits this bug.
I believe that *every* Fortran program using an inline function
with a complex argument hits the bug, though I'm not certain.
It's possible that, since it's a subreg bug, using double precision
complex variables in certain places would avoid the bug. I'll do
some experiments tomorrow.