Yes, my pull request was just merged within the last couple weeks (thanks
to everyone involved btw!), and the only changes left are the rest of the
ARM changes Nikolay is referring to.
On Thu, Apr 25, 2013 at 8:05 AM, Miguel de Icaza
miguel.de.ic...@gmail.comwrote:
Hey,
If it is not merged,
Hi,
On Sat, Mar 2, 2013 at 9:12 PM, zezba9000 zezba9...@gmail.com wrote:
Hi Elijah, I've been trying to find official place to discuss NaCl for
Mono.
Do you have a web page or forum area you prefer to use for this? If there
is no official place to discuss nacl for mono I would rly recommend
Hi,
Just sending a friendly ping for this. It's been a couple weeks with no
movement.
-Elijah
On Thu, Jan 31, 2013 at 3:22 PM, Elijah Taylor elijahtay...@google.comwrote:
FYI: I've rebased these changes into an easier to review pull request
here: https://github.com/mono/mono/pull/540
FYI: I've rebased these changes into an easier to review pull request here:
https://github.com/mono/mono/pull/540
On Fri, Jan 25, 2013 at 4:37 PM, Elijah Taylor elijahtay...@google.comwrote:
Hello Mono friends,
I've just put up a pull request for the latest in NaCl Mono changes:
https
Hello Mono friends,
I've just put up a pull request for the latest in NaCl Mono changes:
https://github.com/mono/mono/pull/538
As mentioned in the description, this does represent two years worth of
changes, but it's still relatively small. If it would be easier to review
in parts I'm open to
Hi Mono folks,
Sorry in advance if this is spam for the dev list.
If you're interested in using Mono in Native
Clienthttps://developers.google.com/native-client/,
it's now available from the NaCl SDK:
https://groups.google.com/forum/?fromgroups#!topic/native-client-discuss/hHYJbE-IL2M.
If
Hi,
I've not seen anything like that myself, but I'll admit we haven't run NaCl
Mono through many production level environments yet, so there may be
something there that's been previously undetected.
However, we've run embedded in Unity3D (their entire scripting engine uses
Mono) and only had to
If it's worth anything, changing null checks to NREs would also severely
cripple Native Client support in Mono. NREs rely on hardware signals if I'm
not mistaken, and we don't support that currently (and probably not for a
long time if ever) in NaCl. We've actually had to rewrite bits of
Hi,
Take a look at this:
https://github.com/elijahtaylor/mono/blob/master/mono/mini/genmdesc.c
This includes a dummy implementation of __nacl_suspend_thread_if_needed for
that file. It wasn't merged into mono's head because it's a temporary
measure and won't be required long term.
Essentially
:
Hi,
I merged your changes to mono's master except for the following:
runtime/mono-wrapper.in
mono/mini/genmdesc.c
nacl/
Zoltan
On Thu, Jan 6, 2011 at 2:22 AM, Elijah Taylor elijahtay...@google.comwrote:
Ok, I'll check out the changes/info you mentioned
to return pagesize aligned memory, isn't that
enough ?
Zoltan
On Thu, Jan 6, 2011 at 8:14 PM, Elijah Taylor elijahtay...@google.comwrote:
This bit of code runs for our AOT compiler, but not for our JIT (in that
case, it's a native 32-bit app that defines
AM, Elijah Taylor elijahtay...@google.comwrote:
Page alignment would be good enough, but I wasn't clear because I had
forgotten some details. When I saw this behavior we were using the dummy
implementation of mono_valloc which falls back on malloc, which I don't
believe we use anymore
have these
changes upstream.
-Elijah
On Thu, Jan 6, 2011 at 11:50 AM, Elijah Taylor elijahtay...@google.comwrote:
Also, if any of the memory allocation routines don't get a larger alignment
like pages, and instead just use MIN_ALIGN, yet pass in a larger alignment
requirement
anything else
you need from me.
-Elijah
On Tue, Jan 4, 2011 at 10:55 AM, Elijah Taylor elijahtay...@google.comwrote:
Replies inline:
On Tue, Jan 4, 2011 at 10:30 AM, Zoltan Varga var...@gmail.com wrote:
Hi,
Some comments:
- the patch changes IMT_REG to AMD64_R11 in the non-nacl case, I'm
rebase your master branch on
top of master to fix the few conflicts which has surfaced due to changes to
mono master ?
Zoltan
On Wed, Jan 5, 2011 at 8:23 PM, Elijah Taylor elijahtay...@google.comwrote:
Hi Zoltan,
I've addressed all of the issues you pointed out (minus
, check_usable() in aot-runtime.c checks this flag.
Zoltan
On Thu, Jan 6, 2011 at 2:10 AM, Zoltan Varga var...@gmail.com wrote:
Hi,
On Thu, Jan 6, 2011 at 1:24 AM, Elijah Taylor elijahtay...@google.comwrote:
Zoltan,
I've rebased from mono's master branch and fixed all
. In truth I'm more worried about future Mono changes
accidentally breaking NaCl behavior. I'm planning on getting some automated
testing implemented soon to combat this though.
On Tue, Dec 21, 2010 at 9:12 PM, Elijah Taylor elijahtay...@google.comwrote:
Greetings Mono developers!
*[tl;dr
Hi Rodrigo,
On Sat, Dec 25, 2010 at 5:01 AM, Rodrigo Kumpera kump...@gmail.com wrote:
The patchset is indeed huge and will take quite some review effort to get
it in. I'll start by reviewing the bug fixes then move to ILP32 support.
Yes, sorry about that. I would have loved to have sent
Greetings Mono developers!
*[tl;dr very large patch for Native
Clienthttp://www.chromium.org/nativeclient support
hosted here https://github.com/elijahtaylor/mono, would love feedback and
many eyes to look at it]
*
I'm back with another round of changes for supporting Google's Native Client
Hi, saw this thread from a few days ago and wanted to clarify:
On Sun, Oct 31, 2010 at 9:35 AM, Brian Luczkiewicz br...@sooloos.comwrote:
And are you sure that __native_client_codegen__ on OSX should influence the
file name extension for shared libraries?
Since __native_client_codegen__
for default but thats not a big
problem.
Zoltan
On Mon, Aug 2, 2010 at 8:05 PM, Elijah Taylor
elijahtay...@google.comwrote:
Regarding TARGET_NACL, I'm not sure if that's quite the same as the
other TARGET_ defines. AFAIK all of the TARGET_ defines are generally
AM, Elijah Taylor
elijahtay...@google.comwrote:
Hi, here's an updated patch with your feedback addressed. I re-based
the diff closer to head revision (r160382) to include the other changes of
ours that already landed, as well as make sure we're still compatible with
current Mono development
Great, glad to hear I made the right choices in those type changes. Thanks
for the update.
I was hoping for a little more feedback on the x86 codegen changes,
particularly from anyone with expertise in the code generation aspects of
mono. There's no rush on this, but it would be nice to have
.
Zoltan
On Tue, Jun 22, 2010 at 7:29 PM, Elijah Taylor elijahtay...@google.comwrote:
Greetings Mono Developers,
Attached is a patch to support 32-bit x86 code generation for Google
Native Client (http://code.google.com/p/nativeclient/). I
24 matches
Mail list logo
