From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>,
"Christoph Höger" <christoph.hoeger@tu-berlin.de>,
"caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Closing the performance gap to C
Date: Mon, 19 Dec 2016 17:41:26 +0100 [thread overview]
Message-ID: <1482165686.4629.28.camel@gerd-stolpmann.de> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CFB9581@IRSMSX102.ger.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2326 bytes --]
Michael,
look here, it's the "definitive source":
https://github.com/ocaml/ocaml/blob/trunk/asmcomp/amd64/proc.ml
Windows is in deed different. I don't have enough insight into the
register spilling algorithm to say whether this has a significant
effect, though. OCaml code never keeps registers alive, and thus I
would bet the spilling algorithm is designed for that, and it is
probably not tried to move values preferably to xmm6-15 in order to
avoid spilling during C calls. But that's just a hypothesis... Does
somebody know?
Gerd
Am Montag, den 19.12.2016, 14:52 +0000 schrieb Soegtrop, Michael:
> Dear Gerd,
>
> >
> > When you call a C function like cos it is likely that this
> > happens because the C calling conventions do not preserve the FP
> > registers
> > (xmm*). This could be improved if the OCaml compiler tried
> > alternate places for
> > temporarily storing FP values:
> For Windows this doesn't seem to be true. See e.g.:
>
> https://msdn.microsoft.com/en-us/library/ms235286.aspx
>
> which states that XMM0..XMM5 are volatile, while XMM6..XMM15 must be
> preserved.
>
> I think for Linix you are right. I couldn't find a better reference
> than Wikipedia:
>
> https://en.wikipedia.org/wiki/X86_calling_conventions
>
> see "System V AMD64 ABI" there.
>
> This reference contains a good overview, which matches the above data
> in table 4:
>
> http://www.agner.org/optimize/calling_conventions.pdf
>
> So on Windows, there is for sure no need to save XMM6..XMM15, while
> on Linux this seems to be an issue.
>
> Best regards,
>
> Michael
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Christian Lamprechter
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
>
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-12-19 16:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 13:01 Christoph Höger
2016-12-17 13:02 ` Christoph Höger
2016-12-19 10:58 ` Soegtrop, Michael
2016-12-19 11:51 ` Gerd Stolpmann
2016-12-19 14:52 ` Soegtrop, Michael
2016-12-19 16:41 ` Gerd Stolpmann [this message]
2016-12-19 17:09 ` Frédéric Bour
2016-12-19 17:19 ` Yotam Barnoy
2016-12-21 11:25 ` Alain Frisch
2016-12-21 14:45 ` Yotam Barnoy
2016-12-21 16:06 ` Alain Frisch
2016-12-21 16:31 ` Gerd Stolpmann
2016-12-21 16:39 ` Yotam Barnoy
2016-12-21 16:47 ` Gabriel Scherer
2016-12-21 16:51 ` Yotam Barnoy
2016-12-21 16:56 ` Mark Shinwell
2016-12-21 17:43 ` Alain Frisch
2016-12-22 8:39 ` Mark Shinwell
2016-12-22 17:23 ` Pierre Chambart
2016-12-21 17:35 ` Alain Frisch
2016-12-19 15:48 ` Ivan Gotovchits
2016-12-19 16:44 ` Yotam Barnoy
2016-12-19 16:59 ` Ivan Gotovchits
2016-12-21 9:08 ` Christoph Höger
2016-12-23 12:18 ` Oleg
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=1482165686.4629.28.camel@gerd-stolpmann.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=christoph.hoeger@tu-berlin.de \
--cc=michael.soegtrop@intel.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