perspective over the next few releases.
The 0.4 series of Orc releases will be API and ABI compatible, and
-will be incompatible with the 0.5 series when it comes out. It is
-anticipated that 0.5 will follow in a few months.
+will be incompatible with the 0.5 series when it comes out. The first
+release of the 0.5 series is anticipated to coincide with the release
+of GStreamer 1.0.
Features:
- An application can add rules for converting existing or new opcodes
to binary code for a specific target.
- - Current targets: SSE, MMX, ARM, Altivec, and TI C64x+. (ARM is very
- limited and c64x only produces source code.) The NEON target is not
- open source and can be licensed separately from Entropy Wave. (This
- will change soon.)
+ - Current targets: SSE, MMX, ARM, Altivec, NEON, and TI C64x+. (ARM
+ is very limited and c64x only produces source code.)
- Programs can optionally be emulated, which is useful for testing, or
if no rules are available to convert Orc opcodes to executable code.
+0.4.5
+=====
+
+This release contains many small improvements related to
+converting GStreamer from liboil to Orc.
+
+The major addition in this release is the mainstreaming of
+the NEON backend, made possible by Nokia.
+
+There is a new experimental option to ./configure,
+--enable-backend, which allows you to choose a single code
+generation backend to include in the library. This is mostly
+useful for embedded systems, and is not recommended in general.
+
+The upcoming release will focus on improving code generation
+for the SSE and NEON backends.
+
+
0.4.4
=====