[pypy-dev] GSoC ideas -- AArch64 JIT backend?

2015-03-16 Thread Manuel Jacob
Hi, I decided that this year is a good time to apply for GSoC. Because I never worked on anything JIT-related, this could be a chance to get started with it. There was some discussion about possible improvements for the ARM backend. Also, some newer ARM processors support a 64-bit executio

Re: [pypy-dev] Language Parser Ontology

2015-03-16 Thread Armin Rigo
Hi, On 16 March 2015 at 12:01, anatoly techtonik wrote: > Yes, but developing a new language in RPython requires choosing a > parser first, no? No. Some of RPython's interpreters are only interpreters, without any parser. I'm not saying yours must be too, but in general we tend not to be too i

Re: [pypy-dev] Language Parser Ontology

2015-03-16 Thread anatoly techtonik
On Mon, Mar 16, 2015 at 1:58 PM, Maciej Fijalkowski wrote: > On Mon, Mar 16, 2015 at 12:49 PM, anatoly techtonik > wrote: >> On Tue, Mar 10, 2015 at 1:32 PM, Amaury Forgeot d'Arc >> wrote: >>> 2015-03-09 19:43 GMT+01:00 anatoly techtonik : I'll start from afar, so that it will be easi

Re: [pypy-dev] Language Parser Ontology

2015-03-16 Thread Maciej Fijalkowski
On Mon, Mar 16, 2015 at 12:49 PM, anatoly techtonik wrote: > On Tue, Mar 10, 2015 at 1:32 PM, Amaury Forgeot d'Arc > wrote: >> 2015-03-09 19:43 GMT+01:00 anatoly techtonik : >>> >>> I'll start from afar, so that it will be easier to understand what I >>> am thinking about.. >>> >>> CFFI uses pycp

Re: [pypy-dev] Language Parser Ontology

2015-03-16 Thread anatoly techtonik
On Tue, Mar 10, 2015 at 1:32 PM, Amaury Forgeot d'Arc wrote: > 2015-03-09 19:43 GMT+01:00 anatoly techtonik : >> >> I'll start from afar, so that it will be easier to understand what I >> am thinking about.. >> >> CFFI uses pycparser, which parses C files, but! uses C compiler >> to strip comments