2017-07-02 14:13 GMT+02:00 Steven D'Aprano :
> That only solves the problem of mysum being modified, not whether the
> arguments are ints. You still need to know whether it is safe to call
> some low-level (fast) integer addition routine, or whether you have to
> go through
On 2017-07-02 02:41 AM, Steven D'Aprano wrote:
On Sat, Jul 01, 2017 at 07:52:55PM -0300, Soni L. wrote:
On 2017-07-01 07:34 PM, Victor Stinner wrote:
Let's say that you have a function "def mysum (x; y): return x+y", do
you always want to use your new IADD instruction here? What if I call
On Sun, Jul 2, 2017 at 10:13 PM, Steven D'Aprano wrote:
>> But that's still a hard problem. Or at very least, it's decidedly
>> non-trivial, and the costs are significant, so the net benefits aren't
>> proven.
>
> In fairness, they are proven for other languages, and they
On Sun, Jul 02, 2017 at 03:52:34PM +1000, Chris Angelico wrote:
> On Sun, Jul 2, 2017 at 3:41 PM, Steven D'Aprano wrote:
> >> Let's say that you do. Given how short it is, it would just get inlined.
> >> Your call of mysum ("a", "b") would indeed not use IADD, nor would it be
On Sun, Jul 2, 2017 at 3:41 PM, Steven D'Aprano wrote:
>> Let's say that you do. Given how short it is, it would just get inlined.
>> Your call of mysum ("a", "b") would indeed not use IADD, nor would it be
>> a call. It would potentially not invoke any operators, but instead
On Sat, Jul 01, 2017 at 07:52:55PM -0300, Soni L. wrote:
>
>
> On 2017-07-01 07:34 PM, Victor Stinner wrote:
> >Let's say that you have a function "def mysum (x; y): return x+y", do
> >you always want to use your new IADD instruction here? What if I call
> >mysum ("a", "b")?
> >
> >Victor
>
>
On 2017-07-01 11:57 PM, rym...@gmail.com wrote:
This is literally PyPy. There's little reason for something like this
to end up in official CPython, at least for now.
It's literally not PyPy. PyPy's internal bytecode, for one, does have
typechecks. And PyPy emits machine code, which is not
This is literally PyPy. There's little reason for something like this to
end up in official CPython, at least for now.
--
Ryan (ライアン)
Yoko Shimomura, ryo (supercell/EGOIST), Hiroyuki Sawano >> everyone
elsehttp://refi64.com
On Jul 1, 2017 at 5:53 PM, > wrote:
On 2017-07-01 07:34 PM, Victor
On Sun, Jul 2, 2017 at 8:52 AM, Soni L. wrote:
> On 2017-07-01 07:34 PM, Victor Stinner wrote:
>>
>> Let's say that you have a function "def mysum (x; y): return x+y", do you
>> always want to use your new IADD instruction here? What if I call mysum
>> ("a", "b")?
>>
>>
On 2017-07-01 07:34 PM, Victor Stinner wrote:
Let's say that you have a function "def mysum (x; y): return x+y", do
you always want to use your new IADD instruction here? What if I call
mysum ("a", "b")?
Victor
Let's say that you do. Given how short it is, it would just get inlined.
Your
Let's say that you have a function "def mysum (x; y): return x+y", do you
always want to use your new IADD instruction here? What if I call mysum
("a", "b")?
Victor
___
Python-ideas mailing list
Python-ideas@python.org
On 2017-06-30 07:17 PM, Victor Stinner wrote:
2017-06-30 17:09 GMT+02:00 Soni L. :
CPython should get a tracing JIT that turns slow bytecode into fast
bytecode.
A JIT doesn't have to produce machine code. bytecode-to-bytecode compilation
is still compilation.
2017-06-30 17:09 GMT+02:00 Soni L. :
> CPython should get a tracing JIT that turns slow bytecode into fast
> bytecode.
>
> A JIT doesn't have to produce machine code. bytecode-to-bytecode compilation
> is still compilation. bytecode-to-bytecode compilation works on iOS, and
>
On 30/06/2017 16:09, Soni L. wrote:
CPython should get a tracing JIT that turns slow bytecode into fast
bytecode.
A JIT doesn't have to produce machine code. bytecode-to-bytecode
compilation is still compilation. bytecode-to-bytecode compilation works
on iOS, and doesn't require deviating
PyPy does basically this. So does the tentative project Pyjion. Also Numba,
but on a pre-function basis. It's not a bad ideas, and one that currently
exists with varying degrees of refinement in several projects. I may have
forgotten a few others. I suppose Brython in a sense.
This is very
On Fri, Jun 30, 2017 at 12:09:52PM -0300, Soni L. wrote:
> CPython should get a tracing JIT that turns slow bytecode into fast
> bytecode.
Are you volunteering to do the work?
--
Steve
___
Python-ideas mailing list
Python-ideas@python.org
CPython should get a tracing JIT that turns slow bytecode into fast
bytecode.
A JIT doesn't have to produce machine code. bytecode-to-bytecode
compilation is still compilation. bytecode-to-bytecode compilation works
on iOS, and doesn't require deviating from C.
(This "internal bytecode"
17 matches
Mail list logo