Re: [HACKERS] [PATCH] Suppress Clang 3.9 warnings
От | Aleksander Alekseev |
---|---|
Тема | Re: [HACKERS] [PATCH] Suppress Clang 3.9 warnings |
Дата | |
Msg-id | 20170220143430.GE12278@e733.localdomain обсуждение исходный текст |
Ответ на | Re: [HACKERS] [PATCH] Suppress Clang 3.9 warnings (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] [PATCH] Suppress Clang 3.9 warnings
|
Список | 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.alekseev@postgrespro.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
В списке pgsql-hackers по дате отправления: