| From: | Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCH] Suppress Clang 3.9 warnings |
| Date: | 2017-02-20 14:34:30 |
| Message-ID: | 20170220143430.GE12278@e733.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In theory - could we just always use our internal strl* implementations?
On Mon, Feb 20, 2017 at 09:26:44AM -0500, Tom Lane wrote:
> Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru> writes:
> > I've just tried to build PostgreSQL with Clang 3.9.1 (default version
> > currently available in Arch Linux) and noticed that it outputs lots of
> > warning messages. Most of them are result of a bug in Clang itself:
> >
> > postinit.c:846:3: note: include the header <string.h> or explicitly
> > provide a declaration for 'strlcpy'
>
> It might be an incompatibility with the platform-supplied string.h
> rather than an outright bug, but yeah, that's pretty annoying.
>
> > The rest of warnings looks more like something we could easily deal with:
>
> It's hard to get excited about these if there are going to be hundreds
> of the other ones ...
>
> regards, tom lane
--
Best regards,
Aleksander Alekseev
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-02-20 14:41:18 | "may be unused" warnings for gcc |
| Previous Message | Tom Lane | 2017-02-20 14:26:44 | Re: [PATCH] Suppress Clang 3.9 warnings |