All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [Patch v2 3/3] rust: new package
Date: Sat, 9 Jul 2016 22:48:25 +0200	[thread overview]
Message-ID: <d3d8e020-e7e1-3c27-0fd9-078710f1292c@gmail.com> (raw)
In-Reply-To: <20160709142533.5d4e34b6@itchy>

Hi Eric,

Le 09/07/2016 ? 14:25, Eric Le Bihan a ?crit :
> Hi!
> 
> Le Tue, 5 Jul 2016 12:11:13 +0200,
> Romain Naour <romain.naour@gmail.com> a ?crit :
> 
>> Le 24/06/2016 ? 21:46, Eric Le Bihan a ?crit :
>>> This new package provides the compiler for the Rust programming
>>> language.
>>>
>>> Currently, only the host variant is built.
>>>
>>> The internal build process is as follows:
>>>
>>>  1. rustc-stage0, provided by rust-bootstrap, is used to build
>>>     rustc-stage1.
>>>  2. rust-stage1 builds the final Rust compiler (rust-stage2)
>>>     and the standard library for the host architecture.
>>>  3. the standard library for the target architecture is build.
>>>
>>> The Rust compiler uses LLVM as its backend, compiled with support
>>> for x86, ARM, PowerPC and MIPS architectures.  
>>
>> rust build it's own bundled copy of llvm if it's not available on the
>> host. If host-rust require a llvm compiler we need to add llvm
>> support in Buildroot first.
>>
>> I have some WIP patches about llvm/clang, if you want to take a look:
>> https://github.com/RomainNaour/buildroot/tree/clang-llvm
> 
> Indeed, having host-rust depends on host-llvm may be added later.

I don't think it's a good idea to use the LLVM bundled in Rust since the
dependency on Rust and LLVM will be mixed in the rust package. It will be
difficult to maintain the package in the future.

For example, LLVM needs to be build with gcc >= 4.7 on the host, so the rust
package must depends on BR2_HOST_GCC_AT_LEAST_4_7.

> AFAIK, the copy of LLVM bundled in Rust only contains optimizations.

Do you know if there is some custom patch in LLVM bundled by Rust and if an
external LLVM compiler can be used ?

> In any case, a version of LLVM/clang will have to be built and this takes a
> very long time... Maybe disabling support for some architectures
> will speed it up (I haven't checked). I'll try your patch.

This is the responsibility to the host-llvm package to enable the required
optimizations on which host-rust must depends on. Also it would be possible to
build LLVM only for the architecture selected in Buildroot.

In the end, I think LLVM should be part of the toolchain package, that way it
would be possible to use a prebuild toolchain and only rebuild rust.

Best regards,
Romain

> 
> Regards,
> 

      reply	other threads:[~2016-07-09 20:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 19:46 [Buildroot] [Patch v2 0/3] Add support for the Rust programming language Eric Le Bihan
2016-06-24 19:46 ` [Buildroot] [Patch v2 1/3] jemalloc: new package Eric Le Bihan
2016-07-05  9:09   ` Romain Naour
2016-07-05  9:14   ` Thomas Petazzoni
2016-07-05 17:14   ` Thomas Petazzoni
2016-06-24 19:46 ` [Buildroot] [Patch v2 2/3] rust-bootstrap: " Eric Le Bihan
2016-07-05  9:47   ` Romain Naour
     [not found]     ` <20160709143638.778d7964@itchy>
2016-07-09 20:05       ` Romain Naour
2016-06-24 19:46 ` [Buildroot] [Patch v2 3/3] rust: " Eric Le Bihan
2016-07-05 10:11   ` Romain Naour
2016-07-09 12:25     ` Eric Le Bihan
2016-07-09 20:48       ` Romain Naour [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=d3d8e020-e7e1-3c27-0fd9-078710f1292c@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@busybox.net \
    /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.