unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Emacs 21.4a segmentation fault on startup (gcc 4.0, Solaris 8)
Date: Sat, 21 May 2005 12:48:49 +0300	[thread overview]
Message-ID: <01c55dea$Blat.v2.4$6f5fb1c0@zahav.net.il> (raw)
In-Reply-To: <E1DZFTk-0003mx-0o@fencepost.gnu.org> (message from Richard Stallman on Fri, 20 May 2005 17:56:24 -0400)

> From: Richard Stallman <rms@gnu.org>
> Date: Fri, 20 May 2005 17:56:24 -0400
> Cc: bug-gnu-emacs@gnu.org
> 
> -Wall warns about a lot of things that are not wrong, and causes
> more trouble than it is worth.  I agreed to implement -Wall on the
> explicit understanding that we would NOT adopt the goal to change our
> code so that -Wall would not warn.

Except that latest versions of GCC by default enable more and more
warnings that previously belonged to -Wall.  Warnings such as these
for example:

    regex.c: In function `re_search_2':
    regex.c:4231: warning: comparison is always true due to limited range of data type

This warning is a terrible nuisance in a complex macro, for example.

> If there is a specific kind of warning that would be useful here,
> there is probably an -f option to enable that specific kind of
> warning.  That might be a good thing to use for Emacs.

Agreed.

      reply	other threads:[~2005-05-21  9:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 18:21 Emacs 21.4a segmentation fault on startup (gcc 4.0, Solaris 8) Andrew Koenig
2005-05-18 22:44 ` Richard Stallman
2005-05-19 14:36   ` Kevin Rodgers
2005-05-19 19:00     ` Eli Zaretskii
2005-05-20 21:56     ` Richard Stallman
2005-05-21  9:48       ` Eli Zaretskii [this message]

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='01c55dea$Blat.v2.4$6f5fb1c0@zahav.net.il' \
    --to=eliz@gnu.org \
    --cc=bug-gnu-emacs@gnu.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).