On Sun, Mar 22, 2009 at 12:29 AM, Jerry Quinn wrote:
> Ian Lance Taylor wrote:
>>
>> Jerry Quinn writes:
>>
>>
>>>
>>> 2009-03-21 Jerry Quinn
>>>
>>> * config/i386/i386.c (ix86_function_specific_save): Don't check
>>> range of enum values.
>>>
>>
>> I still don't know why I don't see this,
Ian Lance Taylor wrote:
Jerry Quinn writes:
2009-03-21 Jerry Quinn
* config/i386/i386.c (ix86_function_specific_save): Don't check
range of enum values.
I still don't know why I don't see this, but this is OK for the
gcc-in-cxx branch.
Do I need to take any actions befo
Jerry Quinn writes:
> 2009-03-21 Jerry Quinn
>
>* config/i386/i386.c (ix86_function_specific_save): Don't check
>range of enum values.
I still don't know why I don't see this, but this is OK for the
gcc-in-cxx branch.
Thanks.
Ian
Jerry Quinn wrote:
Joseph S. Myers wrote:
On Sat, 21 Mar 2009, Ian Lance Taylor wrote:
../.././gcc/config/i386/i386.c:3282: error: comparison is always true
due to limited range of data type
#define IN_RANGE(VALUE, LOWER, UPPER) \
((unsigned HOST_WIDE_INT) (VALUE) - (unsigned HOST_
Joseph S. Myers wrote:
On Sat, 21 Mar 2009, Ian Lance Taylor wrote:
../.././gcc/config/i386/i386.c:3282: error: comparison is always true
due to limited range of data type
#define IN_RANGE(VALUE, LOWER, UPPER) \
((unsigned HOST_WIDE_INT) (VALUE) - (unsigned HOST_WIDE_INT) (LOWER) \
On Sat, 21 Mar 2009, Ian Lance Taylor wrote:
> > ../.././gcc/config/i386/i386.c:3282: error: comparison is always true
> > due to limited range of data type
>
> #define IN_RANGE(VALUE, LOWER, UPPER) \
> ((unsigned HOST_WIDE_INT) (VALUE) - (unsigned HOST_WIDE_INT) (LOWER) \
><= (unsigned HOS
Jerry Quinn writes:
> I just tried to bootstrap the gcc-in-cxx branch, but it fails in stage
> 2. If I expand the macros, the code looks OK to me.
>
> Any suggestions on how to go about tracking this down (if someone else
> doesn't get there first)?
Tobias Schlüter saw the same thing; I don't kn
Hi,
I just tried to bootstrap the gcc-in-cxx branch, but it fails in stage
2. If I expand the macros, the code looks OK to me.
Any suggestions on how to go about tracking this down (if someone else
doesn't get there first)?
Thanks,
Jerry Quinn
/home/jlquinn/gcc/dev/gcc/host-x86_64-unknown