Slava Pestov 1e7893b6ce compiler: FFI is now slightly more efficient when unboxing parameters, only changes data stack height once		2009-10-20 04:31:48 -05:00
..
alias-analysis	compiler.cfg.alias-analysis: fix ##compare where operands are copies	2009-10-01 23:54:19 -05:00
block-joining	…
branch-splitting	…
build-stack-frame	compiler.cfg: remove _gc instruction, it doesn't need to exist, and change GC checks to ensure that the right amount of space is available instead of blindly checking for 1Kb	2009-10-05 05:27:49 -05:00
builder	compiler: FFI is now slightly more efficient when unboxing parameters, only changes data stack height once	2009-10-20 04:31:48 -05:00
checker	Fix the build	2009-09-09 13:44:54 -05:00
comparisons	fold test-vector/branch sequences into a test-vector-branch instruction	2009-10-01 19:53:30 -05:00
copy-prop	…
dataflow-analysis	…
dce	Working on adding support for the new write barrier to optimized code	2009-10-14 02:06:01 -05:00
debugger	add a "test-mr." word to compiler.cfg.debugger equivalent to "test-mr mr."	2009-09-30 11:34:19 -05:00
def-use	compiler: tweak generated code	2009-09-04 03:01:18 -05:00
dominance	…
empty-blocks	…
gc-checks	compiler.cfg: remove _gc instruction, it doesn't need to exist, and change GC checks to ensure that the right amount of space is available instead of blindly checking for 1Kb	2009-10-05 05:27:49 -05:00
hats	Merge branch 'master' of git://factorcode.org/git/factor	2009-10-01 23:14:16 -05:00
instructions	Working on adding support for the new write barrier to optimized code	2009-10-14 02:06:01 -05:00
intrinsics	compiler: on PPC, ANDI, ORI and XORI instructions take an unsigned 16-bit immediate, unlike ADDI, SUBI and MULLI which take a signed 16-bit immediate. The code generator was not aware of this, and so for example '[ >fixnum -16 bitand ]' would generate incorrect code. Split up small-enough? hook into immediate-arithmetic? and immediate-bitwise? and update value numbering to be aware of this. Fixes classes.struct bitfields test failure	2009-10-19 04:58:29 -05:00
linear-scan	compiler.cfg: fix unit tests	2009-10-15 06:01:46 -05:00
linearization	compiler.cfg: remove _gc instruction, it doesn't need to exist, and change GC checks to ensure that the right amount of space is available instead of blindly checking for 1Kb	2009-10-05 05:27:49 -05:00
liveness	…
loop-detection	…
mr	Fix the build	2009-09-09 13:44:54 -05:00
optimizer	compiler.cfg.ssa.destruction: more aggressive coalescing work in progress	2009-09-27 17:17:26 -05:00
parallel-copy	…
predecessors	…
registers	…
renaming	compiler: eliminate boilerplate by centralizing info in declarative INSN: syntax	2009-09-02 06:22:37 -05:00
representations	typo in convert-to-fill-vector?	2009-10-07 12:53:10 -05:00
rpo	…
save-contexts	Fix the build	2009-09-09 13:44:54 -05:00
ssa	compiler.cfg.ssa.destruction: don't coalesce registers with different representations, even if they're in the same register class, since this messes up spilling	2009-09-29 22:28:20 -05:00
stack-frame	…
stacks	compiler.cfg: remove _gc instruction, it doesn't need to exist, and change GC checks to ensure that the right amount of space is available instead of blindly checking for 1Kb	2009-10-05 05:27:49 -05:00
tco	…
useless-conditionals	split unordered and ordered float comparison intrinsics in compiler; generate only unordered comparisons for now	2009-09-08 17:04:26 -05:00
utilities	Fix the build	2009-09-09 13:44:54 -05:00
value-numbering	compiler: on PPC, ANDI, ORI and XORI instructions take an unsigned 16-bit immediate, unlike ADDI, SUBI and MULLI which take a signed 16-bit immediate. The code generator was not aware of this, and so for example '[ >fixnum -16 bitand ]' would generate incorrect code. Split up small-enough? hook into immediate-arithmetic? and immediate-bitwise? and update value numbering to be aware of this. Fixes classes.struct bitfields test failure	2009-10-19 04:58:29 -05:00
write-barrier	compiler.cfg: fix unit tests	2009-10-15 06:01:46 -05:00
cfg.factor	…
summary.txt	…