Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: Andy Ray <andy.ray@ujamjar.com>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
	Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Faster byte code
Date: Sun, 20 Sep 2015 20:57:32 +0200	[thread overview]
Message-ID: <20150920185732.GA19599@notk.org> (raw)
In-Reply-To: <CAHYOizE8G8Kr7vWZfZcn0qJK2X_5X72NR67g3G4kDCjU5pHcMQ@mail.gmail.com>

On Sun, Sep 20, 2015, Andy Ray wrote:
> Thank you for the explanation.  It is interesting that changing
> optimisation levels is something that needs to be done so carefully.
> 

GCC's -O2 optimization level (and -O3 even more) haven't always been as
safe and stable as they currently are. :) 

There are still some compilers easily producing funky outputs used in
production.

Also, I'm wondering whether this change reduces the compiler's own build
times.

-- 
Adrien Nader

      reply	other threads:[~2015-09-20 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-19 22:06 Andy Ray
2015-09-19 22:32 ` Gabriel Scherer
2015-09-19 23:24   ` Andy Ray
2015-09-20 18:57     ` Adrien Nader [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150920185732.GA19599@notk.org \
    --to=adrien@notk.org \
    --cc=andy.ray@ujamjar.com \
    --cc=caml-list@inria.fr \
    --cc=gabriel.scherer@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox