1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
|
0.4.8
=====
Changes:
- Fix Windows and OS/X builds
- Improve behavior in failure cases
- Major improvements for Altivec backend
- Significant documentation additions
Memory for executable code storage is now handled in a much more
controlled manner, and it's now possible to reclaim this memory
after it's no longer needed.
A few more 64-bit opcodes have been added, mostly related to
arithmetic on floating point values.
The orcc tool now handles 64-bit and floating point parameters
and constants.
0.4.7
=====
Changes:
- Lots of specialized new opcodes and opcode prefixes.
- Important fixes for ARM backend
- Improved emulation of programs (much faster)
- Implemented fallback rules for almost all opcodes for
SSE and NEON backends
- Performance improvements for SSE and NEON backends.
- Many fixes to make larger programs compile properly.
- 64-bit data types are now fully implemented, although
there are few operations on them.
Loads and stores are now handled by separate opcodes (loadb,
storeb, etc). For compatibility, these are automatically
included where necessary. This allowed new specialized
loading opcodes, for example, resampling a source array
for use in scaling images.
Opcodes may now be prefixed by "x2" or "x4", indicating that
a operation should be done on 2 or 4 parts of a proportionally
larger value. For example, "x4 addusb" performs 4 saturated
unsigned additions on each of the four bytes of 32-bit
quantities. This is useful in pixel operations.
The MMX backend is now (semi-) automatically generated from
the SSE backend.
The orcc tool has a new option "--inline", which creates inline
versions of the Orc stub functions. The orcc tool also recognizes
a new directive '.init', which instructs the compiler to generate
an initialization function, which when called at application init
time, compiles all the generated functions. This allows the
generated stub functions to avoid checking if the function has
already been compiled. The use of these two features can
dramatically decrease the cost of calling Orc functions.
Known Bugs: Orc generates code that crashes on 64-bit OS/X.
Plans for 0.4.8: (was 2.5 for 4 this time around, not too bad!)
Document all the new features in 0.4.7. Instruction scheduler.
Code and API cleanup.
0.4.6
=====
Changes:
- Various fixes to make Orc more portable
- Major performance improvements to NEON backend
- Minor performance improvements to SSE backend
- Major improvements to ARM backend, now passes regression
tests.
The defaults for floating point operations have been changed
somewhat: NANs are handled more like the IEEE 754 standard,
and denormals in operations are treated as zeros. The NAN
changes causes certain SSE operations to be slightly slower,
but produce less surprising results. Treating denormals as
zero has effects ranging from "slightly faster" to "now possible".
New tool: orc-bugreport. Mainly this is to provide a limited
testing tool in the field, especially for embedded targets
which would not have access to the testsuite that is not
installed.
The environment variable ORC_CODE can now be used to adjust
some code generation. See orc-bugreport --help for details.
orcc has a new option to generate code that is compatible
with older versions of Orc. For example, if your software
package only uses 0.4.5 features, you can use --compat 0.4.5
to generate code that run on 0.4.5, otherwise it may generate
code that requires 0.4.6. Useful for generating source code
for distribution.
New NEON detection relies on Linux 2.6.29 or later.
Plans for 0.4.7: (not that past predictions have been at all
accurate) New opcodes for FIR filtering, scaling and compositing
of images and video. Instruction scheduler, helpful for non-OOO
CPUs. Minor SSE/NEON improvements. Orcc generation of inline
macros.
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
=====
This is almost entirely a cleanup and bug fix release.
- fix register copying on x86-64
- better checking for partial test failures
- fix documention build
- fix build on many systems I don't personally use
- various fixes to build/run on Win64 (Ramiro Polla)
- add performance tests
Next release will merge in the new pixel compositing opcodes
and the SSE instruction scheduler.
0.4.3
=====
New opcodes: all the 32-bit float opcodes from the orc-float
library have been moved into the core library.
New opcodes: splitlw and splitwb, which are equivalent to
select0lw, select1lw, select0wb, and select1wb, except that
the new opcodes split a value into two destinations in one
opcode.
New backend: c64x-c, for the TI C64x+ DSP. This backend only
produces source code, unlike other backends which can produce
both source and binary code. Generating code for this backend
can be done using 'orcc --assembly --target=c64x-c'.
Orc now understands and can generate code for two-dimensional
arrays. If the size of the array is known at compile time,
this information can be used to improve generated code.
Various improvements to the ARM backend by Wim Taymans. The
ARM backend is still experimental.
0.4.2
=====
Bug fixes to C backend. Turns out this is rather important on
CPUs that don't have a native backend.
New features have been postponed to 0.4.3.
0.4.1
=====
This release introduces the orcc program, which parses .orc files and
outputs C source files to compile into a library or application. The
main source file implements the functions described by the .orc source
code, by creating Orc programs and compiling them at runtime. Another
source file that it outputs is a test program that can be compiled and
run to determine if Orc is generating code correctly. In future
releases, the orcc tool will be expanded to output assembly code, as
well as make it easier to use Orc in a variety of ways.
Much of Schroedinger and GStreamer have been converted to use Orc
instead of liboil, as well as converting code that wasn't able to
use liboil. To enable this in Schroedinger, use the --enable-orc
configure option. The GStreamer changes are in the orc branch in
the repository at http://cgit.freedesktop.org/~ds/gstreamer
Scheduled changes for 0.4.2 include a 2-D array mode for converting
the remaining liboil functions used in Schroedinger and GStreamer.
Major changes:
- Add the orcc compiler. Generates C code that creates Orc programs
from .orc source files.
- Improved testing
- Fixes in the C backend
- Fix the MMX backend to emit 'emms' instructions.
- Add a few rules to the SSE backend.
0.4.0
=====
Stuff happened.
|
