Hi,
On Mon, Aug 13, 2012 at 1:44 PM, Michal Bendowski wrote:
> I don't think I introduced any Java 6 specific code. Nevertheless Java
> 6 will be EOL'd soon as well (Scala is dropping Java 6 support in the
> next release for example) so I agree that requiring at least Java 6
> seems like a good i
On Tue, Aug 14, 2012 at 7:11 AM, Brandon Rhodes wrote:
> Alex Gaynor writes:
>
>> The trick is tests! Tests can be run without translating (actually
>> the whole interpreter can, but we like tests :D). Just run `pytest.py
>> pypy/module/numpypy/` and you're running the tests, they take like a
>
Hi,
A quick note:
On Tue, Aug 14, 2012 at 10:59 AM, Maciej Fijalkowski wrote:
> (not sure why your translation take so long)
Because of swapping: translating on a 64-bit Mac requires 5-6 GB of RAM ideally.
A bientôt,
Armin.
___
pypy-dev mailing lis
Here is my jitlog:
>
> https://gist.github.com/3341474
>
>
> I updated my jitlog after the work I did last night. I was able to pull
about 50+ ops out of the jitted code, but still, I'm dealing with the fact
that the JIT doesn't realize it can optimize away my data stack. Around
line 55 in the sta
On Tue, Aug 14, 2012 at 1:38 PM, Timothy Baldridge wrote:
> Here is my jitlog:
>>
>>
>> https://gist.github.com/3341474
>>
>>
> I updated my jitlog after the work I did last night. I was able to pull
> about 50+ ops out of the jitted code, but still, I'm dealing with the fact
> that the JIT doesn'
Also, that 4GB Mac looks like it has at least 4 cores, so Make will fork 4 cc
processes, each of which wants 700-1000MB RAM.
Especially if it's only 2-core with hyperthreading, you'll want to limit the
concurrent compiles to 2 (I forget the exact args to `translate` at the moment,
on the subway
I get the following error during translation on Windows:
error C2036: 'void *' : unknown size
I'm using 32 bit python to do my translation. Is there a known fix for this
error?
Thanks,
Timothy
___
pypy-dev mailing list
pypy-dev@python.org
http://mail
Am 14.08.2012 00:23, schrieb wlavrij...@lbl.gov:
Hi Uwe,
1) During build/translation there were several errors
like "undefined reference to `Reflex::Member::~Member()".
This was caused ".
With some modifications (some insertions of
(lib,"Reflex") e.g. ) in pypy/translator/tool
Hi Timothy,
On Tue, Aug 14, 2012 at 4:26 PM, Timothy Baldridge wrote:
> error C2036: 'void *' : unknown size
Fixed yesterday evening in 9e9b39337354. Indeed,
http://buildbot.pypy.org/nightly/trunk/ shows that Win32 has
successfully built this night.
A bientôt,
Armin.
___
Hi Uwe,
rules in translator/platform/posix.py places $(LDFLAGSEXTRA) before $(OBJECTS)
('$(TARGET)', '$(OBJECTS)', '$(CC_LINK) $(LDFLAGSEXTRA) -o $@ $(OBJECTS)
$(LIBDIRS) $(LIBS) $(LINKFILES) $(LDFLAGS)'),
ah, but that then just means that I should not use the 'link_extra' keyword in
the Exte
Numpy's tests are a good starting point, but they tend to ignore corner
cases such as:
improper arguments,
strange mixtures of options,
passing in virtual ndarrays (lazy evaluation and slices),
empty arrays or scalars,
so we generally start with theirs and add more, trying to retain
compatibilit
>
>
> From a quick glimpse it looks like you might be forced to use
> virtualziables here. this is just a very quick glimpse though
>
So I've been playing around with this for about a day now, and I guess I
don't understand the "vritualizable" requirements. When I try to mark a
something as virtu
12 matches
Mail list logo
