public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: "jit@gcc.gnu.org" <jit@gcc.gnu.org>
Subject: Re: libgccjit 5.2 on Mac OSX Yosemite
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <1439516313.21752.108.camel@surprise> (raw)
In-Reply-To: <CACXZuxccFmTEGoV40Hjjw0yKHgk3qGQ90-NAiCHAOFyndwrizQ@mail.gmail.com>

On Thu, 2015-08-13 at 22:04 +0100, Dibyendu Majumdar wrote:
> Dave,
> 
> I was able to get the JIT compiler working on Mac OS X Yosemite using
> your patch. Attached is the patched home-brew script I used.

Thanks; glad it's working.

As noted in the followup I posted, I've now committed the patch to both
branches.

I've also created this pull request:
  https://github.com/Homebrew/homebrew/pull/42924
requesting that they bring in your change to the homebrew gcc.rb recipe.



> When I reported the JIT compilation speed I reported earlier I forgot
> to mention that I was running on SSD disks. With laptop hard disk
> (5400 rpm) the JIT compiler is obviously even slower - the Lua Tests
> that ran in 1 second in interpreted mode took 1648 seconds in JIT
> mode. Timings below. I think that your work on getting rid of the
> process invocations should be given highest priority as JIT
> compilation times need to be improved significantly.

(nods)

If you get a chance to try gcc trunk, it might be interesting to try the
profiling hooks I added:
  https://gcc.gnu.org/ml/jit/2015-q3/msg00134.html

to see the libgccjit profile for Ravi.

In particular, I'm hoping that the Ravi profile is sufficiently similar
to that from test-benchmark.c so that my optimizations will benefit Ravi
(or maybe there are other unexpected things going on?)

Out of interest, how does this compare to LLVM.  IIRC you had said
libgccjit was taking about 5x longer than LLVM; is that still the case?

> Interpreted mode:
> 
> test done on 13/08/2015, at 21:23:43
> Lua 5.3
> 64-bit integers, 64-bit floats
> cleaning all!!!!
> ......    ---- total memory: 60.0K, max memory: 2.7M ----
> total time: 0.57s (wall time: 1s)
> 
> 
> JIT mode:
> testing date/time
> test done on 13/08/2015, at 21:51:11
> Lua 5.3
> 64-bit integers, 64-bit floats
> cleaning all!!!!
> ......    ---- total memory: 59.9K, max memory: 2.7M ----
> total time: 659.17s (wall time: 1648s)


  reply	other threads:[~2015-08-14  1:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:00 Dibyendu Majumdar
2015-01-01  0:00 ` Dibyendu Majumdar
2015-01-01  0:00   ` David Malcolm [this message]
2015-01-01  0:00     ` Dibyendu Majumdar
2015-01-01  0:00   ` [PATCH, committed] jit: on OS X, add -Wl,-undefined,dynamic_lookup to driver invocation David Malcolm
  -- strict thread matches above, loose matches on Subject: below --
2015-01-01  0:00 libgccjit 5.2 on Mac OSX Yosemite Dibyendu Majumdar
2015-01-01  0:00 ` David Malcolm
2015-01-01  0:00   ` David Malcolm
     [not found]     ` <CACXZuxcMbdLjzv01WyNReKCub=jZW4Qow1iZKz3juYfo-vEk=w@mail.gmail.com>
2015-01-01  0:00       ` David Malcolm
2015-01-01  0:00         ` Dibyendu Majumdar

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=1439516313.21752.108.camel@surprise \
    --to=dmalcolm@redhat.com \
    --cc=jit@gcc.gnu.org \
    --cc=mobile@majumdar.org.uk \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).