Preprocessor condition fix

Started by Christian Ullrichabout 10 years ago6 messageshackers
Jump to latest
#1Christian Ullrich
chris@chrullrich.net

Here is a one-line patch to fix a wrong preprocessor condition in
pg_regress, found because the VS 2015 compiler warns on the cast in the
32-bit branch where apparently earlier versions did not.

According to git grep, this is the only place where WIN64 is used
without the leading underscore.

--
Christian

Attachments:

0001-Fixed-preprocessor-condition-WIN64-_WIN64.patchtext/plain; charset=UTF-8; name=0001-Fixed-preprocessor-condition-WIN64-_WIN64.patchDownload+1-2
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Christian Ullrich (#1)
Re: Preprocessor condition fix

Christian Ullrich <chris@chrullrich.net> writes:

Here is a one-line patch to fix a wrong preprocessor condition in
pg_regress, found because the VS 2015 compiler warns on the cast in the
32-bit branch where apparently earlier versions did not.

Pushed, thanks.

According to git grep, this is the only place where WIN64 is used
without the leading underscore.

Hm, my grep found another one ...

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#3Christian Ullrich
chris@chrullrich.net
In reply to: Tom Lane (#2)
Re: Preprocessor condition fix

* Tom Lane wrote:

Christian Ullrich <chris@chrullrich.net> writes:

According to git grep, this is the only place where WIN64 is used
without the leading underscore.

Hm, my grep found another one ...

Oh, sorry. I saw that one, but thought it was intentional because _WIN64
is defined automatically anyway.

--
Christian

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#4Tom Lane
tgl@sss.pgh.pa.us
In reply to: Christian Ullrich (#3)
Re: Preprocessor condition fix

Christian Ullrich <chris@chrullrich.net> writes:

* Tom Lane wrote:

Hm, my grep found another one ...

Oh, sorry. I saw that one, but thought it was intentional because _WIN64
is defined automatically anyway.

Oh? Then we should not need that one (the /D switch in win32.mak) at all.
Should we just remove it?

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#5Christian Ullrich
chris@chrullrich.net
In reply to: Tom Lane (#4)
Re: Preprocessor condition fix

* From: Tom Lane [mailto:tgl@sss.pgh.pa.us]

Christian Ullrich <chris@chrullrich.net> writes:

* Tom Lane wrote:

Hm, my grep found another one ...

Oh, sorry. I saw that one, but thought it was intentional because _WIN64
is defined automatically anyway.

Oh? Then we should not need that one (the /D switch in win32.mak) at all.
Should we just remove it?

We have both confirmed several times that nothing depends on it. I think it can go.

--
Christian

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

#6Tom Lane
tgl@sss.pgh.pa.us
In reply to: Christian Ullrich (#5)
Re: Preprocessor condition fix

Christian Ullrich <chris@chrullrich.net> writes:

* Tom Lane wrote:

Oh? Then we should not need that one (the /D switch in win32.mak) at all.
Should we just remove it?

We have both confirmed several times that nothing depends on it. I think it can go.

Done.

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers