unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "otadmor ." <otadmor@gmail.com>
Cc: oub@mat.ucm.es, emacs-devel@gnu.org
Subject: Re: [SOLVED] (was: very different start up for emacs master compared with 3 month ago)
Date: Wed, 14 Aug 2019 17:24:01 +0300	[thread overview]
Message-ID: <834l2jsu4e.fsf@gnu.org> (raw)
In-Reply-To: <CAJd1wGKVofFy4PAfyyBYjp=JUVLzkndT6okeDAtzQB=Xb6eFmg@mail.gmail.com> (otadmor@gmail.com)

> From: "otadmor ." <otadmor@gmail.com>
> Date: Wed, 14 Aug 2019 08:19:19 +0300
> Cc: oub@mat.ucm.es, emacs-devel@gnu.org
> 
> I meant issues of emacs with Ofast. If some things are known to be broken on emacs with this. I'm not sure
> gcc man will give notes on emacs.

That option's downsides are not related specifically to Emacs.  The
option causes GCC to use optimizations that can produce invalid
programs.  I don't think anyone has tried it with Emacs, and for a
very good reason: it is not intended for general purpose programs.  I
personally advise to stay away of it, except when building programs
where you understand very well the floating-point numerical aspects of
every single line of code.



      reply	other threads:[~2019-08-14 14:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 15:47 very different start up for emacs master compared with 3 month ago Uwe Brauer
2019-08-09 16:05 ` Eli Zaretskii
2019-08-13 10:51   ` [SOLVED] (was: very different start up for emacs master compared with 3 month ago) Uwe Brauer
2019-08-13 14:29     ` Eli Zaretskii
2019-08-13 18:46       ` otadmor .
2019-08-13 18:55         ` Eli Zaretskii
2019-08-13 21:10           ` otadmor .
2019-08-14  2:36             ` Eli Zaretskii
2019-08-14  5:19               ` otadmor .
2019-08-14 14:24                 ` Eli Zaretskii [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=834l2jsu4e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=otadmor@gmail.com \
    --cc=oub@mat.ucm.es \
    /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).