From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michail Nikolaev <michail(dot)nikolaev(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] fix for C4141 warning on MSVC |
Date: | 2018-01-24 02:19:26 |
Message-ID: | CAEepm=1yQZ1kM89=JVkJRL_1_c6uh1v5HkuvB=j0g7NAU1tCiQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 24, 2018 at 1:42 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
>> On Wed, Jan 24, 2018 at 1:16 PM, Michail Nikolaev
>> <michail(dot)nikolaev(at)gmail(dot)com> wrote:
>>> Just very small fix for C4141 warning
>
>> Thanks. This is similar to the fix I proposed over here:
>> https://www.postgresql.org/message-id/CAEepm%3D2iTKvbebiK3CdoczQk4_FfDt1EeU4c%2BnGE340JH7gQ0g%40mail.gmail.com
>
>> Perhaps we should combine these?
>
> +1. The previous thread seems to have died off with nothing happening,
> but we still have those issues to resolve. I like the idea of making
> the macro be a direct drop-in substitute for "inline" rather than
> something you use in addition to "inline". And if we do that, it
> definitely should expand to plain "inline" if we have no other idea.
Here's one like that.
--
Thomas Munro
http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
fix-warnings-about-always-inline-v2.patch | application/octet-stream | 2.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2018-01-24 02:22:41 | Re: PATCH: Configurable file mode mask |
Previous Message | Amit Kapila | 2018-01-24 02:06:17 | Re: Possible performance regression in version 10.1 with pgbench read-write tests. |