Ya I tried in that way also. Means making double integer as
non-Legitimate_constant.
In my case legitimate_constant_p was looking like this:
int
legitimate_constant_p (rtx X)
{
return (GET_CODE(X)!= CONST_DOUBLE);
}
But it was not generating constant pool when i assigned 64bit no. to a 'long
long' type variable. Rather It was doing all in '.main' function only.
Ian Lance Taylor-3 wrote:
>
> Rajiv KI <rajivkumarsingla@xxxxxxx> writes:
>
>> Now to extend with and learn more i started double integer support. My
>> target size i fixed is 32bit. So to support double integer i want to
>> generate a constant pool. And for generating constant pool i read in
>> gccint
>> doc it says to define TARGET_CANNOT_FORCE_CONST_MEM as TRUE. I tried that
>> but didn't get desired results. Help me to solve it out.
>
> TARGET_CANNOT_FORCE_CONST_MEM should not be defined to be true for an
> ordinary constant. It should only return true for special cases like
> the address of a TLS symbol.
>
> gcc will automatically generate a constant pool when it sees a
> constant which is not LEGITIMATE_CONSTANT_P.
>
> Ian
>
>
--
View this message in context: http://old.nabble.com/generating-constant-pool-tp27337873p27351204.html
Sent from the gcc - Help mailing list archive at Nabble.com.
