Hmmm, I had wondered about that - is LLVM being used in place of the old
compiler?
The old compiler was Java based AS3 -> ABC bytecode.
Is the new one:
AS3 -> ABC bytecode -> LLVM -> bytecode (ARM, ABC, etc.)?
or
AS3 -> LLVM -> bytecode (ARM, ABC, etc.) - with a second path for SWC
files - ABC bytecode -> LLVM -> bytecode (ARM, ABC, etc.).
With my meger understanding of how LLVM worksld , I've guessed that
Adobe would be using LLVM in place of the old compiler since you already
had at least one side of it working from Alchemy (LLVM to ABC) and LLVM
is bidirectional (and plug-able - hence the ARM backend for iPhone) by
design. It also makes sense to use something as robust and well
supported as LLVM, and gain all of it's low level optimizations (does
this obsolete Joa's work?).
I'm pretty sure what I've written is possible with LLVM, but I'm not
certain Adobe is doing that with CS5, because there hasn't been a real
clear post by anyone "official" saying exactly how it works (though
there's been a lot of guessing on various blogs, and on the HaXe list in
particular, as well as some slides in some slideshows that seem to
suggest what I've written).
It's great to hear about compiler improvements either way (thanks!) -
although, some language improvements would be welcome as well. ;-)
On a related note, will the underpinnings be exposed to LLVM to allow
other languages to plugin to CS5 or at least the Flex compiler?
(speaking of which, is the Flex compiler using LLVM yet?)
LOL Sorry for the barrage of questions and stream of thought reply! :-D
Thanks,
Kevin N.
On 11/4/09 1:36 PM, Mike Chambers wrote:
Well, we do another level of optimizations via LLVM (so some of the performance
stuff you mention is addressed).
mike chambers
m...@adobe.com
________________________________________
From: flashcoders-boun...@chattyfig.figleaf.com
[flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Kevin Newman
[capta...@unfocus.com]
Sent: Wednesday, November 04, 2009 10:13 AM
To: Flash Coders List
Subject: Re: [Flashcoders] as3 to iphone app
Bummer. :-(
I was hoping for some better dynamic stuff (duck typing), and some
quicker ways to define (or at least instantiate) throw away static types
(like a static version of an object literal - or some kind of structural
data types). And maybe some performance tools like inline functions, or
static (jit) constructors - or old favs from as2 like private
constructors. C# has some of this kind of stuff. So does HaXe.
Maybe next time.
Kevin N.
On 11/2/09 7:50 PM, Mike Chambers wrote:
age changes, although there are some new APIs.
mike chambers
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
