From: John Wiegley <jwiegley@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Juanma Barranquero" <lekktu@gmail.com>,
"Andreas Röhler" <andreas.roehler@online.de>,
emacs-devel@gnu.org
Subject: Re: Fixing compilation and byte-compilation warnings before 25.1
Date: Fri, 13 Nov 2015 15:00:28 -0800 [thread overview]
Message-ID: <m2wptl33oz.fsf@Vulcan.attlocal.net> (raw)
In-Reply-To: <56460E2B.10603@cs.ucla.edu> (Paul Eggert's message of "Fri, 13 Nov 2015 08:22:03 -0800")
>>>>> Paul Eggert <eggert@cs.ucla.edu> writes:
> I also occasionally run valgrind on Emacs executables (actually, temacs),
> and try to fix the warnings it generates. This is considerably harder to do,
> but is a real nice thing to have on our checklist. (Right now, for example,
> there are a couple of memory-allocation bugs that I really would rather be
> fixing than writing administrative text like this. :-)
I'm also working at getting the Coverity scan of Emacs running again.
Warnings-free may not be practically achievement except in terms of some
"reference machine" (i.e., version of Linux + version of GCC), but having some
form of such a goal is better than not.
John
next prev parent reply other threads:[~2015-11-13 23:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 1:47 Fixing compilation and byte-compilation warnings before 25.1 John Wiegley
2015-11-13 12:18 ` Juanma Barranquero
2015-11-13 14:40 ` Andreas Röhler
2015-11-13 15:37 ` Artur Malabarba
2015-11-14 8:34 ` Andreas Röhler
2015-11-13 15:46 ` John Wiegley
2015-11-13 16:22 ` Paul Eggert
2015-11-13 23:00 ` John Wiegley [this message]
2015-11-14 5:54 ` daniel sutton
2015-11-14 10:58 ` Michael Heerdegen
2015-11-14 18:22 ` daniel sutton
2015-11-15 12:41 ` Michael Heerdegen
2015-11-16 14:15 ` daniel sutton
2015-11-16 23:24 ` Artur Malabarba
2015-11-15 16:07 ` sea-level rise of byte-compilation warnings [was: Fixing...byte-compilation warnings...] Drew Adams
2015-11-15 16:42 ` daniel sutton
2015-11-15 17:38 ` Drew Adams
2015-11-15 17:47 ` daniel sutton
2015-11-15 22:39 ` Drew Adams
2015-11-16 23:48 ` Artur Malabarba
2015-11-16 23:52 ` Drew Adams
2015-11-17 0:09 ` Artur Malabarba
2015-11-17 15:45 ` Drew Adams
2015-11-17 3:59 ` Ivan Andrus
2015-11-14 15:23 ` Fixing compilation and byte-compilation warnings before 25.1 Andy Moreton
2015-11-14 10:55 ` Stephen Leake
2015-11-14 16:00 ` John Wiegley
2015-11-14 18:01 ` Stephen Leake
2015-11-15 9:08 ` David Engster
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=m2wptl33oz.fsf@Vulcan.attlocal.net \
--to=jwiegley@gmail.com \
--cc=andreas.roehler@online.de \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=lekktu@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.