Jump to content
Excelsior Forums

snowman

Excelsior Staff
  • Content count

    0
  • Joined

  • Last visited

Everything posted by snowman

  1. JET RT (root dir)

    JetPerfect and JIT are mutually exclusive. The whole idea of JetPerfect is that it precompiles all classes of your application and therefore can make more optimizations.
  2. To JET marketing: Open-source license?

    There will be some new licensing options introduced soon, so stay tuned. (soon == in 1-2 months )
  3. You seem to have found the most appropriate place to ask this question, congratulations.
  4. SWING to SWT

    http://www.swtguibuilder.com/ http://swingwt.sourceforge.net/ Disclaimer: Neither I nor my colleagues at Excelsior used any of the above.
  5. This is a locked topic to which the moderator posts news about the progress of the Linux port. Click on "Notify of Replies" above to stay tuned. To date, we have ported most of Excelsior JET runtime core to Linux and added ELF support to the linker, which resulted in a succesful compilation and run of the "Hello, Linux world!" application on May 21st. We have also decided to release a public beta ASAP, so be prepared that the first beta will only work from the command-line (but will accept projects created in the JET Control Panel on Windows) and will not provide deployment facilities.
  6. Linux Port Status - v3.6 Final Released!

    Excelsior JET for Linux just debuted! Download your evaluation copy here.
  7. Linux Port Status - v3.6 Final Released!

    Major news are JetPackII port and support for the latest microversions.
  8. You may have read about Multitasking JVM (MVM) in the recent Sun Inner Circle article, at the Barcelona project home page or elsewhere. In case you have not, the idea of MVM is to have one JVM process (in terms of the operating system) host several isolated Java applications, sharing common VM data such as loaded platform classes. To applications, it will appear as if they were run on separate JVMs, which is the only way you can execute several Java programs on one computer today. Beside footprint and startup time reduction, MVM promises to deliver speedup in inter-application communication, because no process switching would be necessary for exchanging data between e.g. a Java application server and a Java database. The downside is that if a fatal bug is hit in the MVM or access violation occurs in a native method, all applications will terminate. Now, consider Excelsior JET. It allows code sharing at the operating system level through DLLs. It delivers startup time reduction through global optimizations and/or executable image optimization. Yes, it does not remove the inter-process communication overhead, but you can think of it as a tradeoff for stability - a fatal error in one application normally does not affect others (except on Win9x). So the only other major advantage of MVM is the common memory manager. Imagine you have a system with 2GB RAM and want to run on it two memory-intensive applications. Because of garbage collection, their maxium heap sizes may not exceed ~1.5GB in total, otherwise excessive paging may occur resulting in radical performance degradation. So you have to explicitly divide this 1.5GB space by specify maximum heap size for each application, e.g. 750MB and 750MB, or 1GB and 500MB, and so on. On an MVM, you may set the maximum heap size for all Java applications, and have a privileged task to dynamically adjust the per-task limits. So in the above scenarion you could set the total limit to 1.5GB and if the privileged control task detects that one application is staying idle with 100M allocated on the heap, it may allow the other one to use up to 1.4 GB of memory. This led me to an idea: what if we enable JET-compiled Java applications to coordinate their memory management? This can be done e.g. via a service/daemon process. Please post your opinions. Did you ever need to run more than one memory-intensive Java application on one system? Was the independency of their memory managemet the show-stopper? Should we implement multi-process heap management facility in Excelsior JET? For details about MVM, check out the papers at the Barcelona project home page
  9. Linux Port Status - v3.6 Final Released!

    Most important is the introduction of the all-new fast JIT compiler, which will surely find its way in the 3.6 release for Windows. JET Setup core was ported, but its user interface is limited to command line. We now test on Mandrake 10 beside other distros. You may wish to check out the new sample (Rhino scripting engine.)
  10. JCE and Java 1.4.2

    See this Knowledge Base article.
  11. Linux Port Status - v3.6 Final Released!

    The big news are NPTL support and JET Control Panel. Now JET works on RedHat 9, Fedora Core 1 and other NPTL-enabled distros.
  12. Linux Port Status - v3.6 Final Released!

    Beta 5 is the first performance-tuned release of Excelsior JET 3.5 for Linux. In our preliminary tests, it outperformed IBM JIT and Sun HotSpot. For details and download, click here.
  13. Debugging JET?

    In short - you cannot. Actually, you should not need to debug your compiled Java code. You have to make sure your program works on the conventional HotSpot VM before compiling it with Excelsior JET. If the complied version does not work then, it is likely to be a configuration issue or maybe a bug in JET. The compiler can produce debug information, but the format is proprietary and only our own debugger XD can read it. We do not make it generally available in order to improve the protection of your compiled programs against reverse engineering.
  14. Upgrade to 3.5

    Your assumption is correct - you have to update the JET RT directory.
  15. Upgrade to 3.5

    The main reasons to upgrade are: New features, the major being support for Endorsed Standards Override and the xjava launcher. Application performance improvement (just a few percent, though some of our tests has speeded up by 20%). Actually this is a side effect of changes aimed at compatibility, not performance. Support for future J2SE microversions (through Maintenance Packs) The upgrade cost to users of v3.15 Pro is $375. If you have an active Maintenance Contract (which you could have purchased at just $150), or if the date of your order for v3.15 is November 25, 2003 or later, you qualify for a free upgrade.
  16. Yes, there will be MP3 (what an acronym) for 3.15 with fixes and support for the latest J2SE 1.3 and 1.4 microversions.
  17. Linux Port Status - v3.6 Final Released!

    Excelsior JET 3.5 beta 4 for Linux fixes numerous bugs, adds samples for jEdit and Jext. Note that the download page has moved. We have finally discovered the cause of a major problem that occured on RedHat 7.x - it has to do with the executable loader in RH7 not following the ELF spec. This is apprently fixed in RH8. Making our linker compatible with RH7 requires much effort, so we have postponed fixing this problem.
  18. GCJ can compile for the Mac, at least here is what its Supported Targets page says: PPC Darwin (including MacOS X) Some kludges needed.
  19. Why there's DOS shell as well?

    See this Knowledge Base Article.
  20. XDS's StdChans.DEF

    1. Which version of XDS are you using? 2. The XDS standard hello.mod sample does not use the StdChans module. Which sample are you talking about?
  21. JRE 1.4.2_01 vs JRE 1.4.2_01

    Another point to consider is that the JRE in JDK\JRE is not redistributable according to its license agreement.
  22. Linux Port Status - v3.6 Final Released!

    Excelsior JET 3.5 for Linux beta 2 release addresses bugs, performance degradation and binary (in)compatibility between Linux versions and distributions. Download here.
  23. Linux Port Status - v3.6 Final Released!

    Excelsior JET 3.5 beta 1 for Linux is available! Download here Omitted are: - JET Setup GUI. A shell script is provided instead. - JET Control Panel. You can migrate projects from the Windows version changing just the path names. - Application deployment facilities (JetPackII and Excelsior Installer) - Documentation. You can access or download Excelsior JET for Windows User's Guide here. All this will appear in future betas. Enjoy!
  24. Linux Port Status - v3.6 Final Released!

    Well, you might say "September ended, and there is no beta available for download." Wait just a little bit more - we are already editing the readme file and adding samples to the package, so you can expect the beta to go out in a day or two.
  25. You do not need to use JNI to call a JET-compiled Java DLL from a JET-compiled Java EXE. If that is what you want to do, please refer to chapter "Dynamic Linking" in the User's Guide and to examples in [tt]samples\DLL[/tt].
×