Horton
Menu

Re: C99 compliance for src/port/snprintf.c

Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

View thread
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Andres Freund <andres@anarazel.de>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Steele <david@pgmasters.net>, pgsql-hackers@lists.postgresql.org
Date: 2018-08-16T12:26:07Z
Lists: pgsql-hackers 
On 16/08/2018 13:18, Andres Freund wrote:
>   checking for ccache gcc option to accept ISO C99... unsupported
> 
>   I suspect that's because of the '-ansi' flag in CFLAGS, not because
>   the compiler is incapable of actually supporting C99.

-ansi is equivalent to -std=c90.  If we make the switch, the build farm
configuration should just probably replace -ansi with -std=c99.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Remove test for VA_ARGS, implied by C99.

  2. Introduce minimal C99 usage to verify compiler support.

  3. Require C99 (and thus MSCV 2013 upwards).

  4. Require a C99-compliant snprintf(), and remove related workarounds.

  5. Try to enable C99 in configure, but do not rely on it (yet).

  6. Make snprintf.c follow the C99 standard for snprintf's result value.

  7. Clean up assorted misuses of snprintf()'s result value.