unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christoph Scholtes <cschol2112@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: sdl.web@gmail.com, emacs-devel@gnu.org
Subject: Re: emacs-20111024-r106182 Windows Binaries
Date: Tue, 25 Oct 2011 19:06:30 -0600	[thread overview]
Message-ID: <867h3s8stl.fsf@googlemail.com> (raw)
In-Reply-To: <E1RIgnR-0006n3-2h@fencepost.gnu.org> (Eli Zaretskii's message of "Tue, 25 Oct 2011 09:12:01 -0400")

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.

>> Just to make sure, is specifying `--no-opt' enough to disable
>> optimizations when configuring or do I have to specify `-O0'
>> explicitely?
>
> Specifying --no-opt is enough.
>
> With --no-opt, -fno-omit-frame-pointer should have no effect, because
> this optimization is turned on by -O1.

Thanks.



  reply	other threads:[~2011-10-26  1:06 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 [this message]
2011-10-26  8:12                   ` Eli Zaretskii
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

  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=867h3s8stl.fsf@googlemail.com \
    --to=cschol2112@googlemail.com \
    --cc=eliz@gnu.org \
    --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 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).