From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: MAXIMUM_ALIGNOF on Windows-32 |
Date: | 2007-07-23 15:29:00 |
Message-ID: | 25805.1185204540@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:
> Tom Lane wrote:
>> Somebody had better double-check that. We don't need to be
>> "pessimistic", we need to be *correct*, because the align values had
>> better match the way the compiler will lay out a C struct. Otherwise
>> struct-based access to catalog rows will fail. (I'm not sure if there
>> are any system catalogs with float8 or int64 columns, but I'd sure not
>> want to find out that we couldn't have one because of misconfiguration
>> of MSVC builds.)
> How do I double-check this?
The configure script checks it by declaring
struct {
char pad;
TYPE field;
} foo
and then measuring offsetof(foo, field), for each interesting TYPE.
>> I see though that the comment in pg_config.h.win32 claims it was derived
>> from mechanically-generated configure output, so unless that's lying
>> it should be OK already.
> It's not - it started out as a copy of the output of ./configure on mingw.
"Started out as"? Good luck keeping it in sync, if it's not
mechanically created.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2007-07-23 15:39:01 | Re: MAXIMUM_ALIGNOF on Windows-32 |
Previous Message | Andrew Dunstan | 2007-07-23 15:26:27 | Re: COPYable logs |