all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: eliz@gnu.org, enometh@meer.net, emacs-devel@gnu.org
Subject: Re: (select-window nil) crash with gcc-8.2.0
Date: Mon, 08 Apr 2019 18:08:06 -0400	[thread overview]
Message-ID: <E1hDcQw-0003Cc-Si@fencepost.gnu.org> (raw)
In-Reply-To: <442c5daa-7efa-45a2-25af-9df66ac1c479@cs.ucla.edu> (message from Paul Eggert on Sun, 7 Apr 2019 11:42:59 -0700)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > Yes, it's -O2 -Os that's the problem. -Os is rarely used so I doubt whether we 
  > need to work around the GCC bug.

Have we reported the GCC bug?  That's very important, since we want
GCC to work correctly.

-- 
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  reply	other threads:[~2019-04-08 22:08 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 [this message]
2019-04-09  4:39             ` Paul Eggert
2019-04-09 23:13               ` Richard Stallman
2019-04-10  2:01                 ` Paul Eggert
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

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

  git send-email \
    --in-reply-to=E1hDcQw-0003Cc-Si@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=enometh@meer.net \
    /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.