Re: Win64 warnings about size_t

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Win64 warnings about size_t
Date: 2010-01-01 19:33:07
Message-ID: 17991.1262374387@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Fri, Jan 1, 2010 at 20:12, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> This shouldn't be a problem for the same reason that casting size_t to
>> int is not a problem in the PostgreSQL backend code, but perhaps writing
>> 1L << ... would fix it.

> 1L didn't fix it. 1LL did, however.

... and would break things on many many other platforms.

Use "(Size) 1" instead of "1" if you really want to suppress this.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-01-01 19:41:10 Re: win32 socket definition
Previous Message Magnus Hagander 2010-01-01 19:28:13 Re: Win64 warnings about size_t