unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: rms@gnu.org
Cc: enometh@meer.net, emacs-devel@gnu.org
Subject: Re: (select-window nil) crash with gcc-8.2.0
Date: Tue, 9 Apr 2019 19:01:41 -0700	[thread overview]
Message-ID: <d519e7c7-c7a2-ae13-3397-8f09ba7f6cba@cs.ucla.edu> (raw)
In-Reply-To: <E1hDzvP-0000qw-BO@fencepost.gnu.org>

Richard Stallman wrote:
>    >https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90020
> 
> Thank you.
> 
> It is very very important to report the bugs we find in other
> programs, both GNU packages and others.

Yes, a bug was going to be reported one way or another, by Madhu or by me. This 
test case seems to have uncovered two GCC bugs, one introduced in GCC 4.9.x in 
2014, and one that seems to predate that. Richard Biener is testing an overall 
patch.

I considered putting something into etc/PROBLEMS warning people not to compile 
Emacs with gcc -O2 -Os, but apparently that sort of GCC usage is pretty rare so 
it's not clear it's worth documenting it (plus, the advice is not specific to 
Emacs).



  reply	other threads:[~2019-04-10  2:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07  2:11 (select-window nil) crash with gcc-8.2.0 Madhu
2019-04-07  3:50 ` Eli Zaretskii
2019-04-07  5:19   ` Madhu
2019-04-07  7:13     ` Andreas Schwab
2019-04-07 16:16       ` Eli Zaretskii
2019-04-07 18:33     ` Paul Eggert
2019-04-07 18:38       ` Eli Zaretskii
2019-04-07 18:42         ` Paul Eggert
2019-04-08 22:08           ` Richard Stallman
2019-04-09  4:39             ` Paul Eggert
2019-04-09 23:13               ` Richard Stallman
2019-04-10  2:01                 ` Paul Eggert [this message]
2019-04-11 18:38                   ` Paul Eggert
2019-05-26  6:51     ` finding the pdmp file again Madhu
2019-05-27 10:32       ` Andreas Schwab
2019-05-27 20:13       ` Richard Stallman

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=d519e7c7-c7a2-ae13-3397-8f09ba7f6cba@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=enometh@meer.net \
    --cc=rms@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).