All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-oe][PATCH 1/6] llvm: update 3.5.2 to have a sane ARM JIT for OpenJDK-8
Date: Wed, 21 Oct 2015 16:11:18 +0200	[thread overview]
Message-ID: <20151021141118.GC2556@jama> (raw)
In-Reply-To: <20151021110944.GB2556@jama>

[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]

On Wed, Oct 21, 2015 at 01:09:44PM +0200, Martin Jansa wrote:
> On Wed, Oct 21, 2015 at 12:59:37PM +0200, Martin Jansa wrote:
> > On Wed, Oct 14, 2015 at 08:48:51PM +0200, Jens Rehsack wrote:
> > > 
> > > llvm introduced new JIT technology MCJIT with llvm 3.4 and fixes ARM in 3.5
> > > (see http://llvm.org/releases/3.5.2/docs/ReleaseNotes.html#changes-to-the-arm-backend).
> > > 
> > > Ensure JIT is built with llvm
> > 
> > I'm tempted to leave this one after jethro is branched, unless
> > default LLVM_RELEASE is updated in oe-core/jethro mesa as well.
> > 
> > Otherwise everybody will need to set LLVM_RELASE in their mesa bbappend
> > or we'll need to bbappend it in meta-oe.
> 
> Or better, update this to keep 3.3 as llvm is meant to allow multiple
> versions being built and installed in parallel.

Another reason to keep 3.3 around is build on older hosts, current 3.5
fails in Ubuntu-12.04

| checking whether GCC is new enough... no
| configure: error:
| The selected GCC C++ compiler is not new enough to build LLVM. Please upgrade
| to GCC 4.7. You may pass --disable-compiler-version-checks to configure to
| bypass these sanity checks.

> > What others think?
> > 
> > And was this tested with mesa or just with java?
> > 
> > Regards,
> > 
> > > 
> > > Signed-off-by: Jens Rehsack <sno@netbsd.org>
> > > ---
> > >  meta-oe/recipes-core/llvm/llvm.inc                 |  8 +---
> > >  ...r-output-from-configure-if-CFLAGS-is-set-.patch | 52 ----------------------
> > >  .../{llvm3.3 => llvm3.5}/arm_fenv_uclibc.patch     |  0
> > >  .../llvm/{llvm3.3_3.3.bb => llvm3.5_3.5.2.bb}      | 11 +++--
> > >  4 files changed, 9 insertions(+), 62 deletions(-)
> > >  delete mode 100644 meta-oe/recipes-core/llvm/llvm3.3/Remove-error-output-from-configure-if-CFLAGS-is-set-.patch
> > >  rename meta-oe/recipes-core/llvm/{llvm3.3 => llvm3.5}/arm_fenv_uclibc.patch (100%)
> > >  rename meta-oe/recipes-core/llvm/{llvm3.3_3.3.bb => llvm3.5_3.5.2.bb} (71%)
> 
> 
> 
> -- 
> Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com



-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-10-21 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 18:48 [meta-oe][PATCH 1/6] llvm: update 3.5.2 to have a sane ARM JIT for OpenJDK-8 Jens Rehsack
2015-10-21 10:59 ` Martin Jansa
2015-10-21 11:09   ` Martin Jansa
2015-10-21 14:11     ` Martin Jansa [this message]
2015-10-21 14:24       ` Jens Rehsack
2015-10-21 14:42         ` Martin Jansa
2015-10-21 14:28       ` Otavio Salvador
2015-10-21 14:45         ` Martin Jansa

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=20151021141118.GC2556@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.