Python Front-end to GCC

2013-10-20 Thread Philip Herron
Hey, I've been working on GCCPY since roughly november 2009 at least in its concept. It was announced as a Gsoc 2010 project and also a Gsoc 2011 project. I was mentored by Ian Taylor who has been an extremely big influence on my software development carrer. Gccpy is an Ahead of time implementati

Re: Python Front-end to GCC

2013-10-21 Thread Philip Herron
Hey all, Thanks, i've been working on this basically on my own 95% of the compiler is all my code, in my spare time. Its been fairly scary all of this for me. I personally find this as a real source of interest to really demystify compilers and really what Jit compilation really is under the ho

Re: Python Front-end to GCC

2013-10-21 Thread Philip Herron
On Monday, 21 October 2013 21:26:06 UTC+1, zipher wrote: > On Mon, Oct 21, 2013 at 4:08 AM, Philip Herron > > wrote: > > > Thanks, i've been working on this basically on my own 95% of the compiler > > is all my code, in my spare time. Its been fairly sca

Re: Python Front-end to GCC

2013-10-22 Thread Philip Herron
On Tuesday, 22 October 2013 09:55:15 UTC+1, Antoine Pitrou wrote: > Philip Herron googlemail.com> writes: > > > > > > Its interesting a few things come up what about: > > > > > > exec and eval. I didn't really have a good answer for this at

Re: Python Front-end to GCC

2013-10-22 Thread Philip Herron
On Tuesday, 22 October 2013 10:14:16 UTC+1, Oscar Benjamin wrote: > On 22 October 2013 00:41, Steven D'Aprano > > >>> On the contrary, you have that backwards. An optimizing JIT compiler > > >>> can often produce much more efficient, heavily optimized code than a > > >>> static AOT compiler, an

Re: Python Front-end to GCC

2013-10-23 Thread Philip Herron
On Wednesday, 23 October 2013 07:48:41 UTC+1, John Nagle wrote: > On 10/20/2013 3:10 PM, victorgarcia...@gmail.com wrote: > > > On Sunday, October 20, 2013 3:56:46 PM UTC-2, Philip Herron wrote: > > >> I've been working on GCCPY since roughly november 2009 at lea