caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Dmitry Bely <dbely@mail.ru>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Timing Ocaml
Date: Mon, 10 Jun 2002 16:02:12 +0400	[thread overview]
Message-ID: <sn3v735n.fsf@mail.ru> (raw)
In-Reply-To: <4.3.2.7.2.20020609232056.029ec260@mail.d6.com> (Chris Hecker's message of "Sun, 09 Jun 2002 23:24:29 -0700")

Chris Hecker <checker@d6.com> writes:

>>* The GNU C compiler gcc is recommended, as the bytecode
>>   interpreter takes advantage of gcc-specific features to enhance
>>   performance.
>>What is the nature of these optimizations?
>
> GCC lets you take the address of a label.  You can see in
> byterun/interp.c that it uses a jump table instead of a switch when
> you're using GCC.
>
> At least, that's what it looks like.

I would rather say that gcc allows to force register allocation for some
specific variable, while MSVC always ignore "register" specifier.

#if defined(__GNUC__) && !defined(DEBUG)
[...]
#ifdef __i386__
#define PC_REG asm("%esi")
#define SP_REG asm("%edi")
#define ACCU_REG
#endif
[...]
#endif

/* The interpreter itself */

value interprete(code_t prog, asize_t prog_size)
{
#ifdef PC_REG
  register code_t pc PC_REG;
  register value * sp SP_REG;
  register value accu ACCU_REG;
#else
  register code_t pc;
  register value * sp;
  register value accu;
#endif

In the same time MSVC has very good optimizer and it is very strange, that
two explicit register variables lead to 30% performance gain...

Hope to hear from you soon,
Dmitry


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-06-10 12:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10  5:35 Blair Zajac
2002-06-10  6:24 ` Chris Hecker
2002-06-10 12:02   ` Dmitry Bely [this message]
2002-06-10 12:50     ` Remi VANICAT
2002-06-10 14:19       ` Lionel Fourquaux
2002-06-10 15:01 ` Xavier Leroy
2002-06-10 16:29   ` Dmitry Bely
2002-06-10 16:49     ` Lionel Fourquaux
2002-06-11  8:28       ` Dmitry Bely
2002-06-11  9:08         ` Xavier Leroy
2002-06-11 12:52         ` Mattias Waldau
2002-06-10 18:19   ` Blair Zajac
2002-06-11  9:23     ` Florian Hars

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=sn3v735n.fsf@mail.ru \
    --to=dbely@mail.ru \
    --cc=caml-list@inria.fr \
    /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;
as well as URLs for NNTP newsgroup(s).