all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: C warning in MSYS2 build
Date: Thu, 05 Oct 2017 21:54:40 +0300	[thread overview]
Message-ID: <83inftwhlb.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58oh2NB5LS-FYmntSMg-0edA9keE5=YmsZ7Q-sjhRbJipaQ@mail.gmail.com> (message from Richard Copley on Thu, 5 Oct 2017 18:44:43 +0100)

> From: Richard Copley <rcopley@gmail.com>
> Date: Thu, 5 Oct 2017 18:44:43 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>
> 
> One more warning crept into the MSYS2 build after the recent update to
> the system headers/libraries:
> 
> make[1]: Entering directory '/c/projects/emacs/src'
>   CC       indent.o
> indent.c: In function 'scan_for_column':
> indent.c:69:10: warning: potential null pointer dereference [-Wnull-dereference]
>    return 0;
>           ^
> indent.c:69:10: warning: potential null pointer dereference [-Wnull-dereference]
> indent.c:69:10: warning: potential null pointer dereference [-Wnull-dereference]
> indent.c:69:10: warning: potential null pointer dereference [-Wnull-dereference]
> make[1]: Leaving directory '/c/projects/emacs/src'

Thanks, but it isn't new.  You already reported this very warning in

  http://lists.gnu.org/archive/html/emacs-devel/2017-09/msg00478.html

and I already said here:

  http://lists.gnu.org/archive/html/emacs-devel/2017-09/msg00427.html

that I thought it was a GCC bug.  Paul seemed to confirm that in

  http://lists.gnu.org/archive/html/emacs-devel/2017-09/msg00493.html

I have no idea how to fix this, except by removing -Wnull-dereference
from the warning flags.



  reply	other threads:[~2017-10-05 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-05 17:44 C warning in MSYS2 build Richard Copley
2017-10-05 18:54 ` Eli Zaretskii [this message]
2017-10-05 19:32   ` Paul Eggert
2017-10-05 20:08     ` Richard Copley
2017-10-05 22:44       ` Paul Eggert
2017-10-06 15:16     ` Richard Stallman
2017-10-06 17:23       ` Richard Copley

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83inftwhlb.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rcopley@gmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.