From: Ivan Viso Altamirano <ivanviso123@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Is LLVM bytecode the future ?
Date: Tue, 26 Aug 2014 11:15:03 +0000 [thread overview]
Message-ID: <CAJoFwWucyJwKWyks1J4yCHED6vUZaK9RtmhYHL3xSFsgYyFtMA@mail.gmail.com> (raw)
In-Reply-To: <loom.20140825T215059-771@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 2446 bytes --]
But what i mean is native code . Anyway , what about compile to binary
lenguages like java (it won't run as native one , but you will remove a lot
of overhead from the java vm ) , Or simply , a thing like .NET/Mono but at
low level .
And , of course , thanks for the answer , and your project is very
interesting , i'll take a look .
2014-08-25 20:00 GMT+00:00 James <wireless@tampabay.rr.com>:
> Ivan Viso Altamirano <ivanviso123 <at> gmail.com> writes:
>
> >
> > This has little to do with Gentoo , but still it is a interesting debate
> .
> > You can compile a great sort of programing lenguages to llvm bytecode :
> > C(++) , java , Objetive C(++) , C# , Haskell , Rust ... And a lot more .
> > On the other side , you CAN'T compile , lenguages like python or perl .
>
> I was just reading about Clang on the gentoo wiki and llvm. It seems that
> most
> of the portage tree now compiles with Clang. Some packages, although not
> listed, do compile but give runtime errors. It'd be great to know what does
> not compile and what compiles but has run problems with the code.
>
>
> > The interesting part is that a feature under developement : It can
> > decompile C(++) code to LLVM bytecode , (only if it not use plataform
> > specific libraries or assembly code ) So , you can easily port your
> > favourite X86 privative application to ARM or PPC , Just wonderfull .
>
> There are many methodologies for running codes develop for one system on
> top of another system. "Gentroid" is another example [1]. Massively
> parallel
> Arm based servers are much closer than most realize; they will have several
> mechanisms to run many popular binaries to provide for quick penetration
> into the server/workstation markets. In less than a year, many complex
> softwares will be "re-worked" to take advantage some some very
> powerful new paradigms in processor, memory and buss semantics.....
>
> hth,
> James
>
> [1] https://code.google.com/p/gentroid/
>
> [2] posted to gentoo embedded:
>
>
> Little update on my project Gentroid:
> gentroid is now in the layman remote list, also I made a video, which
> show the Hello World app running on Gentoo:
> https://www.youtube.com/watch?v=8mdiUHNbPFs, but the source code is not
> yet available because the main repository is too big. I sent a request
> to the google code hosting team and I hope they will raise the limit, so
> I can upload the complete source code.
>
> Regards,
> Simon
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3236 bytes --]
prev parent reply other threads:[~2014-08-26 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-25 19:45 [gentoo-user] Is LLVM bytecode the future ? Ivan Viso Altamirano
2014-08-25 19:55 ` [gentoo-user] " Ivan Viso Altamirano
2014-08-25 20:00 ` James
2014-08-26 11:15 ` Ivan Viso Altamirano [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=CAJoFwWucyJwKWyks1J4yCHED6vUZaK9RtmhYHL3xSFsgYyFtMA@mail.gmail.com \
--to=ivanviso123@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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