public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Wilson <wilson@cygnus.com>
To: Weiwen Liu <liu@hepvms.physics.yale.edu>
Cc: egcs@cygnus.com
Subject: Re: complex support on alpha
Date: Thu, 02 Oct 1997 20:35:00 -0000	[thread overview]
Message-ID: <199710030335.UAA16564@cygnus.com> (raw)
In-Reply-To: <Pine.OSF.3.96.971002000152.22469A-100000@hepunix1.physics.yale.edu>

	egcs on alpha-dec-osf4.0 fails to generate correct code for
	gcc.c-torture/execute/complex-5.c 
	in the testsuite, because gcc does not calculate correctly the number of
	registers needed for 'float __complex__'.  Instead of 2 registers, gcc
	says only one register is needed. 

It has been broken ever since the initial implementation.  There is a general
problem that __complex__ X fails if X is half the word size or smaller.
For instance, __complex__ short will fail on any 32 bit machine in the same
way that __complex__ float fails on the alpha.  It would be nice to see this
fixed.

Hopefully it can be fixed in a way that doesn't require changes to
every target.  If the alpha.h file requires fixes to make __complex__ float
work, then that implies that every tm.h file needs fixes to fix the general
__complex__ problem.

Jim

  parent reply	other threads:[~1997-10-02 20:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-01 21:03 Weiwen Liu
1997-10-01 22:34 ` Richard Henderson
1997-10-02  9:22   ` Weiwen Liu
1997-10-02 10:46     ` Richard Henderson
1997-10-05 16:16   ` Weiwen Liu
1997-10-05 18:28     ` Richard Henderson
1997-10-02 20:35 ` Jim Wilson [this message]
1997-10-04 14:33   ` Kamil Iskra
1997-10-04 18:29     ` Richard Henderson

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=199710030335.UAA16564@cygnus.com \
    --to=wilson@cygnus.com \
    --cc=egcs@cygnus.com \
    --cc=liu@hepvms.physics.yale.edu \
    /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).