GNU bug report logs - #76559
31.0.50; [-O3 + PGTK] Crash when 'copying as kill'/'killing word'

Previous Next

Full log

View this message in rfc822 format

From: Po Lu <luangruo <at> yahoo.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: Pip Cet <pipcet <at> protonmail.com>, eggert <at> cs.ucla.edu, iura.mail <at> gmail.com, marian.iurie <at> gmail.com, michael.albinus <at> gmx.de, 76559 <at> debbugs.gnu.org, stefankangas <at> gmail.com
Subject: bug#76559: 31.0.50; [-O3 + PGTK] Crash when 'copying as kill'/'killing word'
Date: Thu, 27 Feb 2025 21:30:36 +0800

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Thu, 27 Feb 2025 12:22:36 +0000
>> From: Pip Cet <pipcet <at> protonmail.com>
>> Cc: Po Lu <luangruo <at> yahoo.com>, marian.iurie <at> gmail.com,
>> michael.albinus <at> gmx.de, iura.mail <at> gmail.com, 76559 <at> debbugs.gnu.org,
>> Stefan Kangas <stefankangas <at> gmail.com>, Paul Eggert
>> <eggert <at> cs.ucla.edu>
>> 
>> "Eli Zaretskii" <eliz <at> gnu.org> writes:
>> 
>> > I believe we should recommend against using -O3.  Too many bad bugs
>> 
>> If we do that, can we include link time optimization in that?  I find
>> LTO'd code extremely difficult to read, since things like the calling
>> convention no longer apply (even when a function call isn't inlined, LTO
>> can still conclude that some registers survive the call and reuse them
>> even though the calling convention disagrees).

It's marginally easier to read the RTL (which ultimately becomes no more
than a Lisp-like representation of the assembly but with some tree
expressions and analogous details preserved for reference,
e.g. non-inlined procedure calls).

> Maybe we should also recommend against LTO.  Paul, WDYT about this?

I think there is no occasion to compile Emacs with any optimization
options besides -O2.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.