From: Eli Zaretskii <eliz@gnu.org>
To: Christoph Scholtes <cschol2112@googlemail.com>
Cc: sdl.web@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-20111024-r106182 Windows Binaries
Date: Wed, 26 Oct 2011 04:12:51 -0400 [thread overview]
Message-ID: <E1RIybT-0004rY-6H@fencepost.gnu.org> (raw)
In-Reply-To: <867h3s8stl.fsf@googlemail.com> (message from Christoph Scholtes on Tue, 25 Oct 2011 19:06:30 -0600)
> From: Christoph Scholtes <cschol2112@googlemail.com>
> Cc: sdl.web@gmail.com, emacs-devel@gnu.org
> Date: Tue, 25 Oct 2011 19:06:30 -0600
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I didn't realize the above crash was with your binaries. If it was,
> > it's probably a different problem. Leo, if you have a way of
> > reproducing this, please run under GDB and produce a backtrace, or
> > better yet, show the recipe (and file a bug report).
>
> I looked around in the tdm bug tracker but I couldn't find any issues
> related to optimization or `-fno-omit-frame-pointer' reported for 4.6.1
> so far.
The problem is not specific to tdm, it's a general problem of any GCC
port to Windows that uses the Microsoft runtime. I posted here the
URL that describes the bug in more detail. It only happens with
`-fomit-frame-pointer', i.e. with any optimization at or above -O1 (if
I understand correctly the GCC manual and if the manual is accurate).
next prev parent reply other threads:[~2011-10-26 8:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 3:56 emacs-20111024-r106182 Windows Binaries Christoph Scholtes
2011-10-25 5:19 ` Leo
2011-10-25 5:27 ` Christoph Scholtes
2011-10-25 5:46 ` Leo
2011-10-25 8:00 ` Eli Zaretskii
2011-10-25 8:36 ` Leo
2011-10-25 8:56 ` Eli Zaretskii
2011-10-25 9:14 ` Leo
2011-10-25 12:32 ` Christoph Scholtes
2011-10-25 13:12 ` Eli Zaretskii
2011-10-26 1:06 ` Christoph Scholtes
2011-10-26 8:12 ` Eli Zaretskii [this message]
2011-10-26 3:25 ` Leo
2011-10-26 8:37 ` [h-e-w] " Eli Zaretskii
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=E1RIybT-0004rY-6H@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=cschol2112@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@gmail.com \
/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.