Re: [RFC/RFA] Allow cygwin native to compile with --enable-64-bit-bfd

Christopher Faylor
2007-11-25T22:12:45Z

On Sun, Nov 25, 2007 at 02:08:23PM -0500, Daniel Jacobowitz wrote:
>On Sun, Nov 25, 2007 at 12:32:08PM -0500, Christopher Faylor wrote:
>> On Sat, Nov 24, 2007 at 05:47:27PM -0500, Daniel Jacobowitz wrote:
>> >On Sat, Nov 24, 2007 at 04:07:08PM -0500, Christopher Faylor wrote:
>> >> > if (!target_read_string
>> >> >- ((CORE_ADDR) current_event.u.DebugString.lpDebugStringData, &s, 1024,
>> >> >0)
>> >> >+ ((CORE_ADDR) addr, &s, 1024, 0)
>> >>
>> >> How can coercing something to uintptr_t and then to CORE_ADDR achieve
>> >> anything? How does the double coercion help?
>> >
>> >Just the warning. CORE_ADDR will be long long,
>> >current_event.u.DebugString.lpDebugStringData will apparently be a pointer.
>>
>> And the warning is?
>
>Cast from pointer to integer of different size. Casts are the way
>we've handled it elsewhere in GDB, but I wouldn't complain about a
>wrapper; casting host pointers to CORE_ADDRs is an action we try to
>keep to a minimum anyway.

I wouldn't mind a double cast either, if there is precedent for that.

cgf