[pypy-dev] Faster PyPy build

2025-07-21 Thread PIERRE AUGIER via pypy-dev
e! I guess this trend (decrease of build time) could help PyPy development. Pierre ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3//lists/pypy-dev.python.org M

[pypy-dev] Re: PyPy v7.3.20 was released

2025-07-04 Thread Simon Cross via pypy-dev
Thanks, Matti! ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3//lists/pypy-dev.python.org Member address: arch...@mail-archive.com

[pypy-dev] PyPy v7.3.20 was released

2025-07-04 Thread matti picus via pypy-dev
I have released v7.3.20 of pypy2.7 and pypy3.11. No big featurs, but a number of bug fixes and compatibility updates. Please check it out. Matti ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org

[pypy-dev] Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-06-06 Thread matti picus via pypy-dev
On Fri, Jun 6, 2025 at 12:41 PM PIERRE AUGIER via pypy-dev wrote: > > Thanks for the advice. Interestingly, I can confirm that there was a clear > slowdown in the hpy-0.0.4 branch: fbfb93b991eb is indeed 3 times slower than > 5a77b3ed145a (which is as slow as current PyPy). >

[pypy-dev] Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-06-06 Thread PIERRE AUGIER via pypy-dev
- Mail original - > De: "Carl Friedrich Bolz-Tereick" > À: "PIERRE AUGIER" , "PyPy Developer > Mailing List" > Envoyé: Jeudi 5 Juin 2025 09:53:42 > Objet: Re: [hpy-dev] Re: [pypy-dev] Re: [Numpy-discussion] Better > compatibility of the

[pypy-dev] Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-06-05 Thread CF Bolz-Tereick via pypy-dev
HPy in general), please tell me! Pierre ___________ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3//lists/pypy-dev.python.org Member address: arch...@mail-archive.com

[pypy-dev] Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-06-03 Thread PIERRE AUGIER via pypy-dev
- Mail original - > De: "matti picus via hpy-dev" > À: "PyPy Developer Mailing List" , "Ralf Gommers" > , "hpy-dev" > > Envoyé: Vendredi 2 Mai 2025 10:05:51 > Objet: [hpy-dev] Re: [pypy-dev] Re: [Numpy-discussion] Better compat

[pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-18 Thread Marcus Harnisch
On 06/05/2025 14.23, CF Bolz-Tereick via pypy-dev wrote: If PyPy 3.12., 3.13 and 3.14 are supposed to happen, we'll need other contributors to become interested in working on these features. So far, we are not aware of any such person, but I'm certainly happy to support anyone who w

[pypy-dev] Re: [Numpy-discussion] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-15 Thread PIERRE AUGIER via pypy-dev
efined classes with Numpy arrays attributes. PyPy has this very nice property that Python abstractions can be used "for free" (without any cost in terms of performance). * "yet" because there are some plans to improve that. Pierre ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-07 Thread Techran CO via pypy-dev
___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-06 Thread CF Bolz-Tereick via pypy-dev
On 2025-05-02 10:05, matti picus via pypy-dev wrote: It does not appear there will be a PyPy 3.12. I'll expand a bit/add my POV/my rephrasing: Matti and I don't have the capacity to keep up with CPython's development on our own. If PyPy 3.12., 3.13 and 3.14 are supposed to hap

[pypy-dev] Re: [hpy-dev] Question about ref counting and non-movable objects

2025-05-05 Thread Simon Cross via pypy-dev
ten to or only read, etc. This also removes a host of possible performance improvements. Indeed in the Python free-threading, extending reference counting to hold more information about which thread an object is being accessed from was a key enhancement. Regards, Simon __________

[pypy-dev] Question about ref counting and non-movable objects

2025-05-05 Thread PIERRE AUGIER via pypy-dev
vable objects. I guess people knowing the subject (for example PyPy or GraalPy devs) could give good arguments on these questions or provide interesting and serious references. Best regards, Pierre ___ pypy-dev mailing list -- pypy-dev@python.org To unsubs

[pypy-dev] Re: [hpy-dev] Re: Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-05 Thread PIERRE AUGIER via pypy-dev
yPy Developer Mailing List" , "Ralf Gommers" > , "hpy-dev" > > Envoyé: Vendredi 2 Mai 2025 10:05:51 > Objet: [hpy-dev] Re: [pypy-dev] Re: [Numpy-discussion] Better compatibility > of the Python scientific/data stack with > fast Python interpreters &g

[pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-02 Thread matti picus via pypy-dev
all good ideas get to win out and become the popular, goto solution. PyPy itself is an example that, unfortunately. Matti _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-04-30 Thread Michał Górny
Hello, I'd like to just add a few data points from my Gentoo experience. On Wed, 2025-04-30 at 07:32 +0200, Ralf Gommers via pypy-dev wrote: > On Tue, Apr 29, 2025 at 11:24 AM PIERRE AUGIER < > pierre.aug...@univ-grenoble-alpes.fr> wrote: > > > > I think gettin

[pypy-dev] Re: [Numpy-discussion] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-04-30 Thread PIERRE AUGIER
- Mail original - > De: "Ralf Gommers via NumPy-Discussion" > À: "Discussion of Numerical Python" > Cc: "hpy-dev" , "pypy-dev" , "ralf > gommers" > Envoyé: Mercredi 30 Avril 2025 07:32:44 > Objet: [Numpy-discussion]

[pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-04-29 Thread Ralf Gommers via pypy-dev
http://www.legi.grenoble-inp.fr > LEGI (UMR 5519) Laboratoire des Ecoulements Geophysiques et Industriels > BP53, 38041 Grenoble Cedex, Francetel:+33.4.56.52.86.16 > ___ > NumPy-Discussion mailing list -- numpy-discuss

[pypy-dev] Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-04-29 Thread PIERRE AUGIER
w.legi.grenoble-inp.fr LEGI (UMR 5519) Laboratoire des Ecoulements Geophysiques et Industriels BP53, 38041 Grenoble Cedex, Francetel:+33.4.56.52.86.16 _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-l

[pypy-dev] Re: FYI: question related to HPy on discuss.python.org

2025-04-28 Thread PIERRE AUGIER
n.org and got > interesting > answers from CPython core devs: > > https://discuss.python.org/t/c-api-working-group-and-plan-to-get-a-python-c-api-compatible-with-alternative-python-implementations/89477 _______ pypy-dev mailing list -- pypy-dev@

[pypy-dev] Re: Are the stdlib test.regrtest supposed to pass?

2025-03-12 Thread Liam Ellison via pypy-dev
the emojis really give it away loll ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Are the stdlib test.regrtest supposed to pass?

2025-03-04 Thread Yury V. Zaytsev
n 4. Mar 2025, at 18:40, Jamima Tariqa via pypy-dev > wrote: > > Hey Miro, > > I completely understand your frustration with tests that run but don’t > actually fail the build—it’s like checking a burger’s freshness by looking at > it but never taking a bite. I recently de

[pypy-dev] Re: Are the stdlib test.regrtest supposed to pass?

2025-03-04 Thread Jamima Tariqa via pypy-dev
or debug failures, I’m happy to contribute my findings! ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Are the stdlib test.regrtest supposed to pass?

2025-02-27 Thread Matti Picus via pypy-dev
be1e/recipe/meta.yaml#L94 _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Are the stdlib test.regrtest supposed to pass?

2025-02-27 Thread Michał Górny
don't fail the build for that? > > How do you use those tests in PyPy? Others can probably tell you more, but PyPy's running the test suite via pytest. As for failing, yes, some are expected to fail. See the buildbots [1] for the current status. [1] https://buildbot.pypy.or

[pypy-dev] Are the stdlib test.regrtest supposed to pass?

2025-02-27 Thread Miro Hrončok
ust that we could see the failure in the logs but don't fail the build for that? How do you use those tests in PyPy? Thanks, -- Miro Hrončok -- Phone: +420777974800 Fedora Matrix: mhroncok _______ pypy-dev mailing list -- pypy-dev@python.org To unsub

[pypy-dev] Bug fix release of v7.3.19

2025-02-26 Thread matti picus via pypy-dev
Matti ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Release of v7.3.18 with python2.7, 3.10, 3.11

2025-02-06 Thread Matti Picus via pypy-dev
___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Users of PyPy2.7 ?

2024-11-18 Thread matti picus via pypy-dev
PyPy, like CPython, contains no telemetry code. All we can go by is feedback we get directly from users, which is very limited. I don't think we have gotten a PyPy2.7 issue reported in quite a while. Matti ___ pypy-dev mailing list -- pypy-dev@pytho

[pypy-dev] Free-threading and PyPy ?

2024-11-18 Thread PIERRE AUGIER
ds, Pierre _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Users of PyPy2.7 ?

2024-11-18 Thread PIERRE AUGIER
Hi PyPy developers and users, Out of curiosity, are you aware of users of PyPy2.7 not related to RPython and internal PyPy ? Do you have stats about such usage ? Best regards, Pierre ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe

[pypy-dev] Re: Minor Bug Report for PyPy

2024-11-07 Thread CF Bolz-Tereick via pypy-dev
, 2024 3:24:31 PM GMT+01:00, Denil Bouafia via pypy-dev wrote: >Hi PyPy Support, > >I'm a frequent user of PyPy, and I wanted to let you know about a minor bug >I recently encountered. I believe sharing this information might be helpful >for your ongoing development and troubleshoo

[pypy-dev] Minor Bug Report for PyPy

2024-11-07 Thread Denil Bouafia via pypy-dev
Bouafia a=b=1 print("starting") if (a*b)==0: while True: continue print("done")a=b=1 print("starting") if (a*b)==0: while True: continue print("done")_______ pypy-dev mailing list -- pypy-dev

[pypy-dev] Re: issue with portable python pypy in alpine linux 3.20.3

2024-10-09 Thread CF Bolz-Tereick via pypy-dev
Hi, What PyPy version is this? Where are you getting the PyPy binary from? The official binaries we release are glibc-based, but alpine uses musl, so I guess it's some kind of alpine package? Cheers, CF On 2024-10-08 17:08, Ophir, Avishay via pypy-dev wrote: Hey, We are gettin

[pypy-dev] Re: issue with portable python pypy in alpine linux 3.20.3

2024-10-09 Thread Dima Tisnek via pypy-dev
Other projects have ran into this before, see e.g. https://github.com/sparklemotion/sqlite3-ruby/issues/434 https://github.com/rust-lang/rust/issues/111285 On Wed, Oct 9, 2024 at 1:28 AM Ophir, Avishay via pypy-dev < pypy-dev@python.org> wrote: > Hey, > > We are getting the follo

[pypy-dev] issue with portable python pypy in alpine linux 3.20.3

2024-10-08 Thread Ophir, Avishay via pypy-dev
that? Thanks, Avishay _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Help me understand why PyPy is so slow in my benchmark

2024-09-23 Thread Jeremy Brown
code is necessary to find out what's wrong. > > > > Sure, here's a link to a copy of the benchmark: > > https://pastebin.com/fR0C6qcB. > > > > I also know the JIT definitely can't optimize the iterative version, > > but even if this is a problem specific to PyPy I wouldn't expect runs > > t

[pypy-dev] Re: Help me understand why PyPy is so slow in my benchmark

2024-09-20 Thread CF Bolz-Tereick via pypy-dev
2024 at 23:06, CF Bolz-Tereick via pypy-dev wrote: Can you share how you are running this function? I tried a few variants, and pypy is often faster than CPython on my attempts, so the rest of your code is necessary to find out what's wrong. I would call that code THE example of whe

[pypy-dev] Re: Help me understand why PyPy is so slow in my benchmark

2024-09-20 Thread CF Bolz-Tereick via pypy-dev
#x27;t expect runs to take twice as long compared to CPython. -Jeremy _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: cfb...@gmx.de #!/usr/bi

[pypy-dev] Re: Help me understand why PyPy is so slow in my benchmark

2024-09-19 Thread Jeremy Brown
27;t expect runs to take twice as long compared to CPython. -Jeremy ___________ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Help me understand why PyPy is so slow in my benchmark

2024-09-18 Thread Armin Rigo via pypy-dev
Hi, On Wed, 18 Sept 2024 at 23:06, CF Bolz-Tereick via pypy-dev wrote: > Can you share how you are running this function? I tried a few variants, and > pypy is often faster than CPython on my attempts, so the rest of your code is > necessary to find out what's wrong. I would

[pypy-dev] Re: Help me understand why PyPy is so slow in my benchmark

2024-09-18 Thread CF Bolz-Tereick via pypy-dev
ot;X" + recurse(num - 10) > >elif num >= 9: >return "IX" + recurse(num - 9) > >elif num >= 5: > return "V" + recurse(num - 5) > >elif num >= 4: > return "IV" + recurse(num - 4) > >elif num

[pypy-dev] Re: Help me understand why PyPy is so slow in my benchmark

2024-09-18 Thread Manuel Jacob
ot;V" + recurse(num - 5) elif num >= 4: return "IV" + recurse(num - 4) elif num >= 1: return "I" + recurse(num - 1) else: return "" -Jeremy [1]: https://pypy.org/performance.html#micro-tuning-tips __

[pypy-dev] Help me understand why PyPy is so slow in my benchmark

2024-09-18 Thread Jeremy Brown
curse(num - 5) elif num >= 4: return "IV" + recurse(num - 4) elif num >= 1: return "I" + recurse(num - 1) else: return "" -Jeremy [1]: https://pypy.org/performance.html#micro-tuning-tips __

[pypy-dev] Operating system package...

2024-09-04 Thread stev...@osfda.org
so working on distro-specific install packages; but it would be nice to open access to any and all pypy users... _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org

[pypy-dev] Re: How to test code that uses weakrefs

2024-09-04 Thread Christian Tismer-Sperling
888 ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: How to test code that uses weakrefs

2024-09-02 Thread cpburnz
ensure any unreferenced objects are garbage collected. This may not help with the general use of your library though. ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org

[pypy-dev] How to test code that uses weakrefs

2024-09-02 Thread Dima Tisnek
issue a warning for "unused" resources, by virtue of them missing from the weak container when we expect the user code to keep the reference around. Is there a good idiom or some way to support this behaviour with pypy? Thanks, Dima Tisnek ________

[pypy-dev] Release of PyPy7.3.17

2024-08-29 Thread matti picus
I released a new PyPy. Please try it out. Highlights include a new RISCV backend, an updated pyrepl, and some nice speedups. Release note: https://doc.pypy.org/en/latest/release-v7.3.17.html Matti ___ pypy-dev mailing list -- pypy-dev@python.org To

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-08-11 Thread Logan Chien
metimes. It's sometimes hard to write tests without >> testing too many details. Others may have better comments about them. >> Generally, it's OK to look at what you got and compare it with what >> the test expects. If you can come up with a reason for why what you >

[pypy-dev] Re: Windows zip file for pypy3.10-v7.3.16 is not completed

2024-04-23 Thread Matti Picus
.3.16-win64.zip` and now I get the correct download. Matti ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...

[pypy-dev] Re: Windows zip file for pypy3.10-v7.3.16 is not completed

2024-04-23 Thread yanglei
he zip-file > on the download site was incomplete. I have re-uploaded the file, and > the sha356sum hashes should now match. > > Matti > > > ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Windows zip file for pypy3.10-v7.3.16 is not completed

2024-04-23 Thread Matti Picus
. Matti ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Windows zip file for pypy3.10-v7.3.16 is not completed

2024-04-23 Thread yanglei
-v7.3.16-win64.zip Hope you can check with this issue, thanks in advance. Have a nice day! ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org

[pypy-dev] Release of pypy 7.3.16

2024-04-23 Thread Matti Picus
I have released PyPy v7.3.16, which includes - bugfixes for the garbage collector - updates to the upstream stdlib for security issues Please try it out and report any problems. Matti ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-03-01 Thread Logan Chien
he test expects. If you can come up with a reason for why what you > got is correct too, and free of real performance issues, then that's > good enough. > > A bientôt, > Armin > ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-29 Thread Armin Rigo
ct too, and free of real performance issues, then that's good enough. A bientôt, Armin _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-28 Thread Logan Chien
rely dependent on register allocation, and if you run >> it with boehm then the sequence of instruction is slightly different >> and that might be the reason that the bug doesn't show up then. If >> you get two failures with incminimark and none with boehm, then it >> s

[pypy-dev] Fwd:

2024-02-26 Thread Emre Yıldırım
. I will also talk about that in my report and I want to ask if there is any specific reason for this because isn't pypy 3.10 should also be faster in processing cpu's. Kind regards, Emre pypy_experiment.rtf Description: RTF file _______ pypy-d

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-21 Thread Logan Chien
incminimark-only > constructions---but it's also possible the bug is somewhere unrelated > and it's purely bad luck... > > > Armin > ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-19 Thread Armin Rigo
ith boehm, then it sounds more likely that the case involves one of the incminimark-only constructions---but it's also possible the bug is somewhere unrelated and it's purely bad luck... Armin _______ pypy-dev mailing list -- pypy-dev@python.org T

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-19 Thread Logan Chien
2.7 ./pytest.py rpython/jit/backend/test/test_zll_stress_0.py -s -v > > Yes, that's correct. > > > A bientôt, > Armin > _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-18 Thread Armin Rigo
"dummy version of these operations, e.g. with Boehm". > Just to be sure, is the following command correct? > > python2.7 ./pytest.py rpython/jit/backend/test/test_zll_stress_0.py -s -v Yes, that's correct. A bientôt, Armin _______

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-18 Thread Logan Chien
fact that the > log calls must not cause the generated code to change apart from the > calls). It would let me know exactly what happened---that was for one > bug that took me 10 days of hard work, my personal best :-/ > > > A bientôt, > > Armin > ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-16 Thread Armin Rigo
e generated code to change apart from the calls). It would let me know exactly what happened---that was for one bug that took me 10 days of hard work, my personal best :-/ A bientôt, Armin ___________ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe s

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-02-15 Thread Logan Chien
ok only ~6 hrs (wall clock). If it takes a bunch of days on other > architectures, I guess I must multiply `--repeat` by 40 times or run it on > real hardware. I'll try it again after I clear other bugs. > > Regards, > Logan > > On Mon, Jan 29, 2024 at 12:37 AM CF Bolz-Tereick

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-29 Thread Logan Chien
crash > occurred. It took only ~6 hrs (wall clock). If it takes a bunch of days on other architectures, I guess I must multiply `--repeat` by 40 times or run it on real hardware. I'll try it again after I clear other bugs. Regards, Logan On Mon, Jan 29, 2024 at 12:37 AM CF Bolz-Te

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-29 Thread CF Bolz-Tereick via pypy-dev
On 1/29/24 09:27, CF Bolz-Tereick via pypy-dev wrote: This test looks just wrong, in my opinion. Given that the variable name is `fff`, I think it was just meant as a check "does it roughly look like a pointer". So I think somebody just forgot that sys.maxint is not a power of 2 (and t

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-29 Thread CF Bolz-Tereick via pypy-dev
00 --random-seed=1234` and all test are passing. How long does that take, in wall clock time? I think for the other backends we kept it running for a bunch of days after the last crash occurred. Cheers, CF _______ pypy-dev mailing list -- pypy-dev@python.org

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-28 Thread Logan Chien
>>> >> >> >>> >> Cool! Here are a few thoughts I had when I looked at some RISC-V >> >>> >> early documents long ago (warning, it may be outdated): >> >>> >> >> >>> >> Yes, not using the "compress" extension is probably

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-22 Thread Logan Chien
> >>> >> That looks like something a compiler might do, but it's quite a bit > of > >>> >> work both implementation-wise, and it's unclear if it would help > anyway here. > >>> >> > >>> >> About the V extension,

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-21 Thread Maciej Fijalkowski
it's quite a bit of >>> >> work both implementation-wise, and it's unclear if it would help anyway >>> >> here. >>> >> >>> >> About the V extension, I'm not sure it would be helpful; do you plan >>> >> to use it in the same way as our x86-64 vector extension support? A

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-16 Thread Logan Chien
86-64/builds/9219 > for example > > [3] https://foss.heptapod.net/pypy/benchmarks > > [4] > https://buildbot.pypy.org/builders/jit-benchmark-linux-x86-64/builds/4056 > > [5] > > https://buildbot.pypy.org/builders/jit-benchmark-linux-x86-64/builds/4056/steps/shell_9/

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-16 Thread Matti Picus
https://buildbot.pypy.org/builders/jit-benchmark-linux-x86-64/builds/4056/steps/shell_9/logs/stdio [6] https://github.com/pypy/binary-testing ___________ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org htt

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-15 Thread Logan Chien
rd PyPy. (I may be wrong about that.) >> >> >> >> Singlefloats: we don't do any arithmetic on singlefloats with the JIT, >> >> but it has got a few instructions to pack/unpack double floats into >> >> single floats or to

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-15 Thread Logan Chien
t; >> > >> Singlefloats: we don't do any arithmetic on singlefloats with the JIT, > >> but it has got a few instructions to pack/unpack double floats into > >> single floats or to call a C-compiled function with singlefloat > >> arguments. That's

[pypy-dev] Release v7.3.15 of PyPy

2024-01-14 Thread Matti Picus
since they are from a git repo. I plan to release officially later today. Matti ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-11 Thread Maciej Fijalkowski
ents. That's not optional, though I admit I don't know how a C >> compiler compiles these operations if floats are not supported by the >> hardware. But as usual, you can just write a tiny C program and see. >> >> I agree that RV32 can be a more remote goal for now. It should >> simplify a lot

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-09 Thread Logan Chien
I agree that RV32 can be a more remote goal for now. It should > simplify a lot of stuff if you can just assume a 64-bit environment. > Plus all the other points you mention: the hardware may not support > doubles, and may not be supported by Debian... > > > A bientôt, > > Armin Rigo > ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-09 Thread Armin Rigo
supported by the hardware. But as usual, you can just write a tiny C program and see. I agree that RV32 can be a more remote goal for now. It should simplify a lot of stuff if you can just assume a 64-bit environment. Plus all the other points you mention: the hardware may not support doubles,

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-08 Thread Logan Chien
to github we could try out the github discussions platform. I > opened it up at https://github.com/orgs/pypy/discussions. Of course you > are welcome to use IRC if you are comfortable with it. > > > In addition to Maciej's questions: is there only one compilation target > or wo

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-08 Thread Matti Picus
I got it under control, so it would have been better to hold off until it was more completely finished. Something tho think about. Matti _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-08 Thread Maciej Fijalkowski
ly 73 >> pending commits. Each commit has a specific reason for change and >> corresponding test cases (if applicable). >> >> Is it better to just send one GitHub Pull Request containing all of them? >> >> Or, do you prefer one commit per Pull Request? >>

[pypy-dev] Re: Contribute a RISC-V 64 JIT backend

2024-01-07 Thread Logan Chien
ts. Each commit has a specific reason for change and > corresponding test cases (if applicable). > > Is it better to just send one GitHub Pull Request containing all of them? > > Or, do you prefer one commit per Pull Request? > > Thank you. > > Regards, > Logan >

[pypy-dev] Contribute a RISC-V 64 JIT backend

2024-01-07 Thread Logan Chien
e and corresponding test cases (if applicable). Is it better to just send one GitHub Pull Request containing all of them? Or, do you prefer one commit per Pull Request? Thank you. Regards, Logan ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe

[pypy-dev] Re: Moving to github

2024-01-01 Thread CF Bolz-Tereick via pypy-dev
o has both names for many >> branches. We will have to decide which one to keep tracking. >> >> Matti > > >The repo is live, and the issue tracker is open. The post on >https://www.pypy.org/posts/2023/12/pypy-moved-to-git-github.html has more >information. > &g

[pypy-dev] Re: Moving to github

2024-01-01 Thread Matti Picus
The repo is live, and the issue tracker is open. The post on https://www.pypy.org/posts/2023/12/pypy-moved-to-git-github.html has more information. Matti _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le

[pypy-dev] Re: Moving to github

2024-01-01 Thread Simon Cross
PR with blog post approved. ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Re: Moving to github

2023-12-30 Thread Matti Picus
anch names. The git-remote-hg script uses branches/XXX when converting a branch name, but heptapod/gitlab use branch/XXX (without the "es") so the repo has both names for many branches. We will have to decide which one to keep tracking. Matti ____

[pypy-dev] Re: Moving to github

2023-12-30 Thread Maciej Fijalkowski
py and rpython to github. Reasons: > > +1 from me too and many thanks for taking on the work. > _______ > pypy-dev mailing list -- pypy-dev@python.org > To unsubscribe send an email to pypy-dev-le...@python.org > https://mail.python.org/ma

[pypy-dev] Re: Moving to github

2023-12-29 Thread Simon Cross
Hi Matti, On Thu, Dec 28, 2023 at 9:22 AM Matti Picus wrote: > Now that 7.3.14 has been released, I would like to move the canonical > repo for pypy and rpython to github. Reasons: +1 from me too and many thanks for taking on the work. ___ py

[pypy-dev] Re: Is the hash field optimization still present

2023-12-28 Thread Joannah Nanjekye
n teach, but certain when you can program." Alan J. > Perlis* > -- Best, Joannah Nanjekye *"You think you know when you learn, are more sure when you can write, even more when you can teach, but certain when you can program." Alan J. Perlis* _________

[pypy-dev] Re: Moving to github

2023-12-28 Thread Armin Rigo
_ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Is the hash field optimization still present

2023-12-28 Thread Joannah Nanjekye
*"You think you know when you learn, are more sure when you can write, even more when you can teach, but certain when you can program." Alan J. Perlis* _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@

[pypy-dev] Re: Moving to github

2023-12-28 Thread Oliver Margetts
;> - Write a blog post >> >> - Modify the links in the documentation >> >> - Activate the github action in [3] to add a branch note to each git >> commit >> >> >> Anything else? Any suggestions to make the transition easier? >> >> Mat

[pypy-dev] Re: Moving to github

2023-12-28 Thread David Edelsohn
> - Activate the github action in [3] to add a branch note to each git commit > > > Anything else? Any suggestions to make the transition easier? > > Matti > > > [0] https://gist.github.com/mattip/b6752c164a075c2aa53f4069e9c30573 > > [1] https://github.com/piceaTech/node-gitlab-2-gith

[pypy-dev] Moving to github

2023-12-28 Thread Matti Picus
lian/named-branch-action _______ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

[pypy-dev] Release of v7.3.14

2023-12-24 Thread Matti Picus
I have released v7.3.14 of pypy2.7, pypy3.9, and pypy3.10. Please check it out. The main new feature is support for HPy 0.9. There are also bugfixes and smaller enhancements. Matti ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe

[pypy-dev] Re: How do I compile pypy with debug symbols?

2023-12-13 Thread taniyuki246
I can't see the rest of the call stack, so I am trying to compile a debug version of pypy. https://tinyfishing.co ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mai

[pypy-dev] Re: How do I compile pypy with debug symbols?

2023-12-03 Thread Buddy Lumpkin
g about the top-level > > Makefile. It is talking about the Makefile generated along all the > > generated C files in the temporary directory, in > > /tmp/usession-*/testing_1/. > > > > > > Armin Rigo ___ pypy-dev mailing list -- pypy-dev@python.org To unsubscribe send an email to pypy-dev-le...@python.org https://mail.python.org/mailman3/lists/pypy-dev.python.org/ Member address: arch...@mail-archive.com

  1   2   3   4   5   6   7   8   9   10   >