unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 8217@debbugs.gnu.org
Subject: bug#8217: 23.3; Runtime segmentation fault when compiled with -O2 on GNU/Linux
Date: Sat, 06 Aug 2016 09:34:43 -0400	[thread overview]
Message-ID: <8737mi6mx8.fsf@users.sourceforge.net> (raw)
In-Reply-To: <22437.58952.92130.137875@a1i15.kph.uni-mainz.de> (Ulrich Mueller's message of "Sat, 6 Aug 2016 15:29:44 +0200")

tags 8217 unreproducible
close 8217
quit

Ulrich Mueller <ulm@gentoo.org> writes:

>>>>>> On Thu, 04 Aug 2016, npostavs  wrote:
>
>> I guess this is fixed by now?  I usually build --with-toolkit=lucid
>> (which I read in configure.ac is a synonym for athena), and I
>> haven't hit this.
>
> Looking through Gentoo ebuild history, I find that the workaround of
> adding -fno-strict-aliasing to CFLAGS wasn't present for version 24.1,
> and there never were any bugs reported to us. This seems to indicate
> that the problem had disappeared already in early Emacs 24 versions.
>
> However, I also cannot reproduce this any more with Emacs 23.4 and
> GCC 5.4.0 (nor with GCC 4.9.3). So it may well be that this issue
> wasn't with Emacs but with GCC.

Okay, closing as unreproducible.





      reply	other threads:[~2016-08-06 13:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10  8:34 bug#8217: 23.3; Runtime segmentation fault when compiled with -O2 on GNU/Linux Ulrich Mueller
2011-03-10  8:52 ` Andreas Schwab
     [not found]   ` <19832.41051.618372.463060@a1i15.kph.uni-mainz.de>
     [not found]     ` <19832.49227.947125.153989@a1i15.kph.uni-mainz.de>
2011-03-10 18:39       ` Glenn Morris
2011-03-10 11:48 ` Eli Zaretskii
2011-03-10 12:08   ` Ulrich Mueller
2011-03-24 16:26     ` Chong Yidong
2011-03-25  1:17       ` Stefan Monnier
2016-08-05  1:28     ` npostavs
2016-08-06 13:29       ` Ulrich Mueller
2016-08-06 13:34         ` npostavs [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=8737mi6mx8.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=8217@debbugs.gnu.org \
    --cc=ulm@gentoo.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).