From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
Emacs Development <emacs-devel@gnu.org>
Subject: Re: ‘surrogates_to_codepoint’ warnings
Date: Mon, 15 Jan 2018 19:20:41 +0000 [thread overview]
Message-ID: <CAPM58ohZ=aTTXekKYsU280ZPSo_JYXOkTAJXZUN4dBrWQKRqLg@mail.gmail.com> (raw)
In-Reply-To: <838tczz593.fsf@gnu.org>
On 15 January 2018 at 12:16, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 15 Jan 2018 10:39:59 +0100
>> From: martin rudalics <rudalics@gmx.at>
>>
>> Building master currently gets me lots of
>>
>> ../../src/coding.h:680:1: warning: no previous prototype for ‘surrogates_to_codepoint’ [-Wmissing-prototypes]
>>
>> Ignore them?
>
> No, never.
:)
> Should be fixed now.
Below are the C warnings I currently get when building the master
branch, on MSYS2. I've included the warnings from indent.c below
because their text is quite different. I don't know whether they're
any more useful than their previously-discussed emacs-26 counterparts.
The emacs-26 branch built cleanly last time I checked, except for the
warnings in indent.c discussed here:
<https://lists.gnu.org/archive/html/emacs-devel/2017-10/msg00149.html>
CC indent.o
In file included from indent.c:31:0:
indent.c: In function 'scan_for_column':
disptab.h:43:7: warning: potential null pointer dereference [-Wnull-dereference]
? (NILP ((dp)->ascii) \
^~~~~~~~~~~~~~~~~~
indent.c:297:40: note: in expansion of macro 'DISP_CHAR_VECTOR'
width = sanitize_char_width (ASIZE (DISP_CHAR_VECTOR (dp, ch))); \
^~~~~~~~~~~~~~~~
indent.c:516:8: note: in expansion of macro 'MULTIBYTE_BYTES_WIDTH'
MULTIBYTE_BYTES_WIDTH (p, buffer_display_table (), b, wd);
^~~~~~~~~~~~~~~~~~~~~
disptab.h:43:7: warning: potential null pointer dereference [-Wnull-dereference]
? (NILP ((dp)->ascii) \
^~~~~~~~~~~~~~~~~~
indent.c:297:40: note: in expansion of macro 'DISP_CHAR_VECTOR'
width = sanitize_char_width (ASIZE (DISP_CHAR_VECTOR (dp, ch))); \
^~~~~~~~~~~~~~~~
indent.c:516:8: note: in expansion of macro 'MULTIBYTE_BYTES_WIDTH'
MULTIBYTE_BYTES_WIDTH (p, buffer_display_table (), b, wd);
^~~~~~~~~~~~~~~~~~~~~
disptab.h:43:7: warning: potential null pointer dereference [-Wnull-dereference]
? (NILP ((dp)->ascii) \
^~~~~~~~~~~~~~~~~~
indent.c:297:40: note: in expansion of macro 'DISP_CHAR_VECTOR'
width = sanitize_char_width (ASIZE (DISP_CHAR_VECTOR (dp, ch))); \
^~~~~~~~~~~~~~~~
indent.c:516:8: note: in expansion of macro 'MULTIBYTE_BYTES_WIDTH'
MULTIBYTE_BYTES_WIDTH (p, buffer_display_table (), b, wd);
^~~~~~~~~~~~~~~~~~~~~
disptab.h:43:7: warning: potential null pointer dereference [-Wnull-dereference]
? (NILP ((dp)->ascii) \
^~~~~~~~~~~~~~~~~~
indent.c:297:40: note: in expansion of macro 'DISP_CHAR_VECTOR'
width = sanitize_char_width (ASIZE (DISP_CHAR_VECTOR (dp, ch))); \
^~~~~~~~~~~~~~~~
indent.c:516:8: note: in expansion of macro 'MULTIBYTE_BYTES_WIDTH'
MULTIBYTE_BYTES_WIDTH (p, buffer_display_table (), b, wd);
^~~~~~~~~~~~~~~~~~~~~
CC intervals.o
intervals.c: In function 'offset_intervals':
intervals.c:878:20: warning: potential null pointer dereference
[-Wnull-dereference]
if (position == i->position || eobp)
~^~~~~~~~~~
make[1]: Leaving directory '/c/projects/emacs/src'
make[1]: Entering directory '/c/projects/emacs/src'
CC process.o
process.c: In function 'connect_network_socket':
process.c:208:10: warning: 'family' may be used uninitialized in this
function [-Wmaybe-uninitialized]
return close_on_exec (socket (domain, type, protocol));
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
process.c:3320:7: note: 'family' was declared here
int family;
^~~~~~
next prev parent reply other threads:[~2018-01-15 19:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 9:39 ‘surrogates_to_codepoint’ warnings martin rudalics
2018-01-15 12:16 ` Eli Zaretskii
2018-01-15 19:20 ` Richard Copley [this message]
2018-01-15 19:30 ` Paul Eggert
2018-01-15 19:48 ` Richard Copley
2018-01-15 21:38 ` Paul Eggert
2018-01-15 22:19 ` Richard Copley
2018-01-16 3:31 ` Eli Zaretskii
2018-01-16 9:08 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPM58ohZ=aTTXekKYsU280ZPSo_JYXOkTAJXZUN4dBrWQKRqLg@mail.gmail.com' \
--to=rcopley@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).