The .hgignore file got missed when we moved rpython/ out of pypy/. Can
someone take a look at this patch and commit it if it looks good? Thanks.
diff -r f4e2d6247ba9 .hgignore
--- a/.hgignore Sun Feb 24 17:27:31 2013 +0200
+++ b/.hgignore Sun Feb 24 10:41:00 2013 -0700
@@ -35,39 +35,43 @@
^pypy/d
Maciej Fijalkowski writes:
> On Tue, Feb 12, 2013 at 6:57 AM, Justin Bogner wrote:
>> Armin Rigo writes:
>>> Ah, indeed. We declare most arrays as "itemtype x[1]", so gcc complains
>>> when it can prove we do accesses at an index > 0.
>>
>> I
Armin Rigo writes:
> Ah, indeed. We declare most arrays as "itemtype x[1]", so gcc complains
> when it can prove we do accesses at an index > 0.
Is there a good reason not to use the C99 "itemtype x[]" or even the old
GCC extension "itemtype x[0]"? These won't trigger this warning, which
means w
William ML Leslie writes:
> Do remember that the translator actually requires the python 2
> interpreter, that is a fundamental part of the way it works. So
> moving the translator into a different repository now also means
> maintaining two python 2 interpreters.
Ah yes, bootstrapping makes eve
Antonio Cuni writes:
> after some months of work on the py3k branch, I realized that the current
> strategy/workflow does not scale well and thus I'd like to change it.
>
> For those who are not aware, currently we have the default branch where the
> main development is done, and which includes co
Dale Hubler writes:
> I looked at the pypy site but cannot find any supported platforms,
> install guide, etc. I am trying this on RedHat EL 5. I tried the
> binary release, but it also had the same error, no libssl.so.0.9.8,
> which is true, my systems are updated. I must be missing somethin
