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

Christopher Faylor
2007-11-25T17:32:15Z

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?

If this is a problem then it seems like defining a macro (macros are
good m'kay?) to do the coercion rather than sprinkling temporary
variables throughout the code might be a better way to go.

cgf