From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Edelsohn <dje@watson.ibm.com>
To: Dale Johannesen <dalej@apple.com>
Cc: Richard Henderson <rth@redhat.com>, gcc@gcc.gnu.org
Subject: Re: how to fix anti-optimization? 
Date: Fri, 14 Sep 2001 13:02:00 -0000
Message-id: <200109142001.QAA28672@makai.watson.ibm.com>
References: <200109141950.f8EJoNw06758@scv2.apple.com>
X-SW-Source: 2001-09/msg00563.html

	GPRs can contain FP values.  FP constants can be loaded into GPRs.
Why isn't that be appropriate for LEGITIMATE_CONSTANT_P?  The macro is not
a question of which values are valid immediates for FPRs, but for any
registers.  easy_fp_constant values can be loaded directly into a GPR
representing SFmode or DFmode.  That is what the macro represents.

	Given your analysis, it looks like another GCC macro with
overloaded meanings used in too many instances.  Presumably we need the
macro to be expanded to have both a mode and a register class as
arguments.

	Maybe your change still is safe, but your interpretation of the
macro seems incomplete.

David