- 06 May, 2013 1 commit
-
-
Matthias Braun authored
-
- 12 Mar, 2013 2 commits
-
-
Matthias Braun authored
They weren't used in a sensible way and their semantic for non-arithmetic ops was unclear. Also implicitely fixes a bunch of bugs where these where set but no op_index was set at the same time.
-
Matthias Braun authored
oparity_unary, oparity_binary require opindex to be set, which wasn't always the case. Also people seem to expect certain semantics from unops/binops, like being arithmetic operations. So we shouldn't automatically set oparity_XXX.
-
- 12 Dec, 2012 1 commit
-
-
Matthias Braun authored
Just state the copyright and the project the files belong to. You can then find the COPYING file for the whole project.
-
- 04 Dec, 2012 3 commits
-
-
Matthias Braun authored
-
Matthias Braun authored
-
Matthias Braun authored
-
- 03 Dec, 2012 1 commit
-
-
Christoph Mallon authored
-
- 02 Dec, 2012 1 commit
-
-
Christoph Mallon authored
-
- 01 Dec, 2012 1 commit
-
-
Christoph Mallon authored
-
- 08 Nov, 2012 1 commit
-
-
Christoph Mallon authored
It is the job of the frontend to keep loops. These hacks here only worked for some, but not all cases. In particular a more clever SSA-construction algorithm might not place redundant PhiMs, which would render memory before memory-less loops unkept.
-
- 07 Nov, 2012 1 commit
-
-
Christoph Mallon authored
-
- 24 Oct, 2012 1 commit
-
-
Matthias Braun authored
-
- 15 Oct, 2012 1 commit
-
-
Andreas Seltenreich authored
-
- 21 Aug, 2012 2 commits
-
-
Matthias Braun authored
This means floatingpoint calculation in a firm graph must be performed in the mode specified (and may not be performed in a wider mode as before).
-
Matthias Braun authored
-
- 23 Jul, 2012 1 commit
-
-
Matthias Braun authored
Still broken for anything except int f(void) { return 0; } though...
-
- 10 Jul, 2012 1 commit
-
-
Matthias Braun authored
-
- 19 Jun, 2012 2 commits
-
-
Christoph Mallon authored
-
Christoph Mallon authored
-
- 15 Jun, 2012 1 commit
-
-
Matthias Braun authored
-
- 08 Dec, 2011 1 commit
-
-
Matthias Braun authored
-
- 07 Dec, 2011 2 commits
-
-
Matthias Braun authored
memops are nodes that have memory inputs, you can generically query them for their memory input. We can also get rid of get_fragile_op_mem in favor of get_memop_mem.
-
Christoph Mallon authored
-
- 18 Nov, 2011 1 commit
-
-
Matthias Braun authored
We simply always assume that Sel can only return a null pointer if its input is a null pointer.
-
- 17 Nov, 2011 4 commits
-
-
Matthias Braun authored
-
Matthias Braun authored
This should fix all known bugs, make the code easier to read and more robust.
-
Matthias Braun authored
-
Matthias Braun authored
-
- 14 Nov, 2011 1 commit
-
-
Matthias Braun authored
-
- 10 Nov, 2011 1 commit
-
-
Matthias Braun authored
-
- 02 Nov, 2011 2 commits
-
-
Matthias Braun authored
This is the new way of handling switch-jumps. The node contains a table which maps (ranges of) input values to proj numbers. Compared to a Cond-node this results in a clean consecutive sequence of Proj numbers (no searching for a free number for the default_pn anymore) and allows factoring multiple cases jumping to the same block in a single Proj (though we still need the optimisation in cfopt for that).
-
Matthias Braun authored
-
- 06 Sep, 2011 1 commit
-
-
Matthias Braun authored
-
- 01 Jun, 2011 1 commit
-
-
Matthias Braun authored
-
- 31 May, 2011 1 commit
-
-
Matthias Braun authored
-
- 25 May, 2011 2 commits
-
-
Matthias Braun authored
- The pns of X_regular and X_except are annotated in the opcode now. - The memory input is annotated in the opcode now - only nodes with X_regular, X_except are marked fragile
-
Matthias Braun authored
-
- 06 May, 2011 1 commit
-
-
Matthias Braun authored
-
- 28 Apr, 2011 1 commit
-
-
Matthias Braun authored
add unknown_jump opflag for the special case of a jump where we can't directly influence the destination and can't predict/change them
-