- User Since
- Jul 30 2013, 7:58 PM (347 w, 5 d)
Updated tables to more reasonable values.
I"m working on scrubbing the tables and will post a new version when that is done.
Sat, Mar 28
Rebase and fix a bug.
Is this something we can handle in combineSetCCEFLAGS?
This feels subject to DAG combine ordering not folding the cmov+setcc before this combine gets a chance to run. Would this be simpler if we just did it at the intrinsic lowering stage?
Fri, Mar 27
Thu, Mar 26
Remove the vector reduction flag an associated SelectionDAGBuilder code
Add one use check for scalars as well
Wed, Mar 25
Rebase now that I fixed most of the tests to avoid the blacklist
Tue, Mar 24
Mon, Mar 23
Black list instructions that are currently failing tests.
Rebase. I'm going to try to work on the tests or maybe just start blacklisting instructions until we get the tests fixed.
This probably has a hidden side effect on the pass manager construction. Inserting a module pass into the middle of the pipeline effectively introduces a serialization point in the middle of the pipeline. This means all functions have to reach this point in the pipeline before any function can continue. I believe this will cause the Machine IR for all functions to become resident in memory at once. This will substantially increase the memory usage of the compiler.
Sun, Mar 22
Sat, Mar 21
Fri, Mar 20
What should the behavior of the builtin be if the calling function has its own target cpu like attribute((target("arch=sandybridge"))) and that CPU has a different size than the CPU that was passed on the command line?
Thu, Mar 19
Wed, Mar 18
Tue, Mar 17
Fix typo in comment.
Simpler version to think about. Just let Constrained intrinsics handle their own flags completely, and skip them in the common FMF handling.
Mon, Mar 16
Sun, Mar 15
Preserve address space and change size to UnknownSize.
Sat, Mar 14
Fri, Mar 13
Thu, Mar 12
Looks good to me.