Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

Adobe Releases C/C++ To Flash Compiler

Posted by samzenpus on Wed Nov 19, 2008 06:47 PM
from the transmutations dept.
SnT2k writes "Adobe recently released the beta version of Alchemy which compiles C/C++ code into AS3 bytecode (which runs on AVM2) that can run on the Flash or Flex platform and boasts increased performance for computationally-intensive tasks (but still slower than native C/C++). It was demonstrated last year during the Chicago MAX 2007 to run Quake. A few months later it has been demonstrated to run a Python interpreter and Nintendo Emulator. One interesting tidbit is that the thing is built upon the open source LLVM Compiler Infrastructure."
+ -
story

Related Stories

This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • by TheRaven64 (641858) on Wednesday November 19 2008, @06:55PM (#25826287) Homepage Journal
    On the off-chance that someone from Adobe reads this:

    I've been interested in this idea since the presentation at the LLVM dev meeting. I'd be interested in extending clang to use the native ActionScript object model for Objective-C objects, and adding a GNUstep back end to use the native flash drawing primitives so that we can easily port Cocoa apps to run in a browser. Unfortunately, there was no contact information listed anywhere on the presentation or on this site, so I haven't been able to get in touch with anyone at Adobe Labs about this.

  • NES emulator? (Score:3, Interesting)

    by Mr. Sketch (111112) <mister,sketch&gmail,com> on Wednesday November 19 2008, @06:58PM (#25826327)

    Where I can find info on the NES emulator in Flash? That link didn't have any info that I could find.

    I had started such a project a while back, but never quite finished due to poor performance.

  • It has been said (Score:5, Interesting)

    by frictionless man (1140157) on Wednesday November 19 2008, @07:01PM (#25826375)
    It has been said that the reason apple doesn't want flash on their iPhones is that it would create a competing application infrastructure over which they would have no control. I can see this development reinforcing that position.

    This seems to further cement flash as a worthy application environment, especially given the perceived problem in flash appeared to be its inefficiency.
    Looking forward to better flash games... (Or perhaps not if im not wanting to procrastinate).
    • Re: (Score:3, Insightful)

      This seems to further cement flash as a worthy application environment, especially given the perceived problem in flash appeared to be its inefficiency.

      Huh? You think this method is going to give anything remotely resembling the efficiency of native code? Unless the flash script language is really badly written, the performance will be even worse than programs that were manually written in flash.

    • Re:It has been said (Score:4, Interesting)

      by jcr (53032) <jcr@mac. c o m> on Wednesday November 19 2008, @10:30PM (#25828217) Journal

      the perceived problem in flash appeared to be its inefficiency.

      I'd have to say that seeing Flash_enforceLocalSecurity() in the backtrace just about every time Safari crashes would be a somewhat bigger factor in Apple's rejection of Flash.

      -jcr

      • by StreetStealth (980200) on Wednesday November 19 2008, @09:40PM (#25827843) Journal

        I'd be willing to wager that you've used responsibly designed Flash applets before and simply assumed them to be cleverly implemented Javascript because they didn't explode all over the screen in a cavalcade of light and sound.

        Nothing about Flash compels the developer or designer to author something "garish and obnoxious" any more than Javascript or CSS do. Its versatility merely allows for greater abuse.

        • Re: (Score:3, Informative)

          I'd be willing to wager that you've used responsibly designed Flash applets before and simply assumed them to be cleverly implemented Javascript [...]

          I bet he didn't even notice pressing the big f/play button to make it run ;)

          [FlashBlock firefox extension, a godsend; even worth it when you use noscript, for those video players that start playing straight away despite your wishes].

      • Re: (Score:3, Informative)

        Jailbreak it. There's a quake4iphone in Cydia that's been there for months, with hardware acceleration and everything.

  • by Anonymous Coward on Wednesday November 19 2008, @07:03PM (#25826385)

    Wow, I can compile my C/C++ code to run on a slow virtual machine instead of a native cpu architecture.

    I haven't had this much fun ever since I discovered the java Virtual Machine written in java.

    It brings back the heady days of my 8088.

    • Re: (Score:3, Insightful)

      > java Virtual Machine written in java.

      Link? This sounds completely useless, but it would be interesting to look at the source if available.

    • by fm6 (162816) on Wednesday November 19 2008, @08:11PM (#25827095) Homepage Journal

      If you have a complete C++ application that runs fine on native code, then obviously this would be silly. But if you bothered to RTFA, you know that this serves a simple and obvious purpose: reuse. If you need rendering code for your Flash game, and the best code available is in C or C++, it's a lot easier to just recompile the code than it is to hand-translate the code into ActionScript.

          • Re: (Score:3, Interesting)

            OK, sorry to be so hard on you. It turns out that there are copious buttloads of languages that use some sort of bytecode under the hood. The thing that really makes it stick in your mind with Java is just that it's the format that you're expected to distribute your programs in. Contrast that with Python: The reference implementation (CPython) is also a bytecode interpreter. I'm not sure, it may be possible to distribute a python program in bytecode, but I've neither seen nor heard of anyone doing

  • More details (Score:5, Informative)

    by supermansuper (1183487) on Wednesday November 19 2008, @07:21PM (#25826605)
    More details here: http://www.llvm.org/devmtg/2008-08/ [llvm.org] (Look for the topic - Flash C Compiler: Compiling C code to the Adobe Flash Virtual Machine)
    You post your ideas for Adobe here: http://www.adobe.com/cfusion/webforums/forum/categories.cfm?forumid=72&catid=755&entercat=y [adobe.com] These forums are closely watched by the flash player team.
    • by smcdow (114828) on Thursday November 20 2008, @10:10AM (#25832247) Homepage

      More details here: http://www.llvm.org/devmtg/2008-08/ [llvm.org] (Look for the topic - Flash C Compiler: Compiling C code to the Adobe Flash Virtual Machine)

      While scrolling down looking for the Adobe talk, I found this:

      Designflow: using LLVM to compile to Hardware - This project uses LLVM to compile code to a mixed hardware and software implementation. This detects pieces of programs that may be efficiently compiled to VHDL and synthesized them onto an FPGA. The rest of the program is compiled to PowerPC code and uses to drive the FPGA. The system automatically handles data migration and other handshaking between the two systems.

      Waaaayyyy more interesting than LLVM for flash. This is cool!!!

  • by shird (566377) on Wednesday November 19 2008, @07:33PM (#25826749) Homepage Journal

    compiling C/C++ code into AS3 bytcode (which runs on AVM2) that can run on the Flash or Flex platform and boasts increased performance for computationally-intensive tasks

    Increased performance over what exactly? Is there some other 'slower' bytecode that the VM runs? The summary fails to mention this. I don't see how compiling C++ to the AS3 bytecode would be any faster than compiling some Flash language to AS3 bytecode, or writing AS3 bytecode directly. I assume it is the AS3 bytecode itself that is faster, in which case the 'compiling C++' part is irrelevant to the increased performance.

  • by NouberNou (1105915) on Wednesday November 19 2008, @07:36PM (#25826789)
    I have been working on two large enterprise class applications using their Flex/AIR framework and the performance is absolutely dismal!

    The Flash VM is slow beyond belief when getting into large data-structures, event its native array parsing is incredibly slow.

    Object instantiation is slower than molasses. We were averaging about 7 seconds to instantiate about 500 fairly complex objects that in most any other language, compiled or interpreted would have easily been created in a thousandth of that time.

    The Flash VM's garbage collection is perfectly incapable of doing anything that involves long application run-times and leaks memory all over the place, even inside its native low-level components. It got to the point that even doing any proactive cleanup in our code was totally fruitless and I am sorry to add that a lot of the proactive steps we were taking have been left by the wayside because it is utterly hopeless to release all the memory you have taken back to the system.

    Loading an SWF inside another SWF and then disposing of it will not stop the loaded SWF's playback and it does not release it from memory. Instead of Adobe fixing this obvious bug they just added a different method in Flash 10 called "unload and stop" or something like that. This requires anyone who wants to fix this issue to go back and refactor their code!

    There are also numerous inconsistencies between applications that run in Flash and those that run in AIR, even though the code base is the same and the idea is that you do not have to change any obvious code to make it work in one platform or another.

    Even flashes most basic function, doing vector drawings and animations fails horribly under load. We have had to hack and jury-rig numerous fixes in to compensate for Flash's seemingly random graphical glitches.

    If Adobe wants to be taken seriously as a application platform developer, especially one that is used on the desktop they need to get their shit together because right now it feels like a childs toy or half-assed attempt to enter a new market.

    Unfortunately the project, the client, and the management have chosen this path for us and we are stuck with it so I really hope that Adobe gets it together because its been a royal pain doing this sort of work on their platform.
    • by Locke2005 (849178) on Wednesday November 19 2008, @07:54PM (#25826923)
      This is why I'm actually pleased to see Microsoft pushing Silverlight; if nothing else, it forces Adobe to get off their ass and actually make the Flash 10 SDK available platforms other than Mac OS and Windows! I'm still waiting for Flash 8/Flash 9 content to work on my Wii and on my Android G1 phone, since almost all 'net video is using Flash now. (Looks like the Android Flash support will be there pretty soon. I still think Silverlight gave them a powerful incentive to get their act together on this.)
    • by Locke2005 (849178) on Wednesday November 19 2008, @08:12PM (#25827105)
      I have been working on two large enterprise class applications using their Flex/AIR framework...

      I think I see your problem right there... there is nothing like using the right tools for the job, and this is nothing like using the right tools for the job. ;-)

      • Re: (Score:3, Insightful)

        I completely agree... :( But we are stuck with it.

        Really though they are not that big. One is a graphing and reporting application, and another is a web interface for a CMS that we developed in house as a product.

        The first could have been done in Java, or a cross-platform C++ framework like Qt (though that would remove the selling point that it runs on the desktop and the browser), and the second could be done purely in JS, so there were alternatives, maybe more appropriate ones, but they were not taken
    • Re: (Score:3, Interesting)

      I will say the exact opposite. We made a large enterprise application for a UK health insurer. All interface and logic was flash (not even Flex) with custom-built components. It was a lot better than the alternatives (the initial plan was to use ASPX for the interface). It was nice and fast too (the bottlenecks were on the server). By my last count there were over 200K lines of AS code.

      I also made a chess game [flashchess3.com] in AS3. It's not Deep Blue but after optimizations it's fast enough to have fun with (and strong e

    • Re: (Score:3, Interesting)

      We had a similar experience with Flex 2/3. Flash would hold onto objects through invisible references that were almost impossible to track down and release. We even went so far as setting all object properties for all objects to null before unloaded, and still nothing. It got so bad at one point that each user click increased memory usage by 10mb without ever returning it. This problem occurred both with our own custom code and with the base components provided by Adobe/Flex. This leads me to believe that
      • by NouberNou (1105915) on Wednesday November 19 2008, @09:41PM (#25827849)

        Dude,

        Have you stopped to think that maybe your code has something to do with it?

        Yes, many times, and no I do not think my code is ever perfect, or even near perfect, but the proof is in the pudding, you can make very simple test cases and see very obvious drawbacks using just their code/UI components.

        One of the problems with working with Flex is that sometimes you have to do things that seem incredibly retarded to get things done. Look at the extensive use of the callLater method in a lot of the Flex SDK code. This method basically says "ok things aren't done, so do it later." Not only does this seem to just patch a problem with not correctly sequencing your methods to fire when they are able to, but it creates huge memory leaks and is horribly hard to debug as you rarely can see past the point of the callLater in the stack.

        This reminds me of another problem, in the fact that you can not catch run-time errors at the "root/base" level of the Flash/Flex/AIR application, and even better, if you do not have a debug version of Flash player (and forget it in AIR) then it just completely ignores the error and continues on as if nothing has happened. This then causes Flash to start chucking random errors and glitches that might get caught in your own try-catch blocks much, much later, and you will find that code that works perfectly under every imaginable situation is now glitching with really no known cause. Debugging can be quite the nightmare in Flash.

  • why... (Score:3, Insightful)

    by Vexorian (959249) on Wednesday November 19 2008, @08:40PM (#25827383)
    Righty...

    Let's say... SDL gets a flash port, then you basically can turn your simple C++ game into a game that people can run in flash computers without downloading... At least it sounds interesting.

  • by mgiuca (1040724) on Thursday November 20 2008, @08:35AM (#25831293)

    Finally! Java applets are always so full of hassle to get running compared to Flash objects.

    Now I can compile the JVM to Flash and run my Java applets inside Flash - no more need to install those meddlesome Java plugins!

    • by Morgaine (4316) on Wednesday November 19 2008, @11:54PM (#25828757)
      Javascripts vary in quality, but the latest ones are pretty fast:  for example, Javascript V8 (the Javascript from Google's Chrome browser project) is nearly as fast as Lua, which is the fastest widely used scripting language at the moment.

      Here are some basic timings I made just to give a rough feel for the relative speeds (don't read too much into them).  The first entry provides the timings for C, which is obviously compiled, purely as a basis for comparison with the scripting languages.  Note that the times for C are in milliseconds, while the rest are in seconds, lower is better:

      Execution times for recursive F/P factorial(n) to /dev/null
      Langs @ 2008     Times:  n=1         n=170       difference

      C                      0.000 ms      0.090 ms      0.090 ms
      Lua                    0.001 s       0.005 s       0.004 s
      Parrot-opt/iterative   0.013 s       0.018 s       0.005 s
      Parrot/iterative       0.014 s       0.019 s       0.005 s
      V8-Javascript          0.007 s       0.013 s       0.006 s
      Ocaml                  0.022 s       0.029 s       0.007 s
      Python                 0.013 s       0.027 s       0.014 s
      Parrot-opt/recursive   0.013 s       0.029 s       0.016 s
      Mozilla-Javascript     0.001 s       0.018 s       0.017 s
      Perl                   0.002 s       0.021 s       0.019 s
      Nickle                 0.031 s       0.065 s       0.034 s
      Parrot/recursive       0.014 s       0.056 s       0.042 s
      Ruby                   0.041 s       0.095 s       0.054 s
      Lua_on_Parrot          0.303 s       1.314 s       1.011 s

      Although every scripting language is still at least some 50 times slower than compiled C, interpreters and language VMs in general have been improving steadily over recent years, and Javascript in particular is getting a lot of attention now, with more optimizations in the pipeline from all the major players.

      The gap will shrink, guaranteed.

      [Sorry about the Code posting mode, it's not very easy on the eyes ... but Slashdot no longer accepts the <pre> tag in HTML mode for displaying formatted output.]