From: Eli Zaretskii <eliz@gnu.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Buffer size limitation in insdel.c
Date: Thu, 23 Sep 2010 14:15:19 +0200 [thread overview]
Message-ID: <83iq1wvep4.fsf@gnu.org> (raw)
In-Reply-To: <m37hiclo7n.fsf@quimbies.gnus.org>
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 23 Sep 2010 12:59:56 +0200
>
> There were no comments on my -Wconversion post, so I thought there was
> no interest in making the int/EMACS_INT overflows go away.
You have a lot to learn about the corporate culture here ;-) Lack of
response does not necessarily mean lack of interest. It just means no
one volunteers yet.
> The bugs are trivial to find with -Wconversion, and most of them are
> easy enough to fix. But some may be more subtle?
Some are, indeed. But those are few and far in between.
> A methodology to fix this up with be for us to compile with
> -Wconversion, pick a file, any file, to work on, fix all the
> -Wconversion warnings in that file, and then see if Emacs still works.
>
> Then check in and move on to the next file. :-)
>
> I'm up for taking a few files, but I'm not up for doing all 5400
> warnings.
I already started, feel free to join, and thanks.
For now, I simply go through the sources by hand, it's easy enough to
spot the obvious problems. In a nutshell, any variable declared as
`int' is a suspect, at least in some source files that are frequent
offenders. When this is out of my way, I will use -Wconversion. That
sounds easier than going through 5000 warnings; YMMV.
next prev parent reply other threads:[~2010-09-23 12:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 12:06 Buffer size limitation in insdel.c Eli Zaretskii
2010-09-22 12:12 ` Lars Magne Ingebrigtsen
2010-09-22 15:20 ` Eli Zaretskii
2010-09-22 12:16 ` David Kastrup
2010-09-23 0:06 ` Stefan Monnier
2010-09-23 0:58 ` Richard Stallman
2010-09-23 7:55 ` Eli Zaretskii
2010-09-23 9:23 ` Leo
2010-09-23 9:30 ` Eli Zaretskii
2010-09-23 10:59 ` Lars Magne Ingebrigtsen
2010-09-23 12:15 ` Eli Zaretskii [this message]
2010-09-23 12:18 ` Lars Magne Ingebrigtsen
2010-09-23 12:47 ` Lars Magne Ingebrigtsen
2010-09-23 13:12 ` Andreas Schwab
2010-09-23 13:22 ` Eli Zaretskii
2010-09-23 13:37 ` Lars Magne Ingebrigtsen
2010-09-23 14:13 ` Eli Zaretskii
2010-09-23 14:21 ` Lars Magne Ingebrigtsen
2010-09-23 14:31 ` Lars Magne Ingebrigtsen
2010-09-23 14:41 ` Eli Zaretskii
2010-09-23 14:49 ` Lars Magne Ingebrigtsen
2010-09-23 15:08 ` Lars Magne Ingebrigtsen
2010-09-23 18:56 ` Eli Zaretskii
2010-09-23 19:02 ` Lars Magne Ingebrigtsen
2010-09-23 19:22 ` Eli Zaretskii
2010-09-24 14:09 ` Richard Stallman
2010-09-24 14:28 ` Eli Zaretskii
2010-09-24 14:38 ` Lars Magne Ingebrigtsen
2010-09-25 13:55 ` Eli Zaretskii
2010-09-25 16:26 ` Lars Magne Ingebrigtsen
2010-09-25 16:38 ` Lars Magne Ingebrigtsen
2010-09-25 9:40 ` Richard Stallman
2010-09-25 10:00 ` Eli Zaretskii
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=83iq1wvep4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
/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).