summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDan Gohman <dan433584@gmail.com>2016-05-16 18:51:03 +0000
committerDan Gohman <dan433584@gmail.com>2016-05-16 18:51:03 +0000
commit6627e5f48bfb5eed33db5676e8a1f0916fd90bd8 (patch)
tree8332e6a23d021ebe059b63901c570e2d0f03d9d3
parentac2088d122204325e30e85bb62ec0ab204f04f1b (diff)
downloadbcm5719-llvm-6627e5f48bfb5eed33db5676e8a1f0916fd90bd8.tar.gz
bcm5719-llvm-6627e5f48bfb5eed33db5676e8a1f0916fd90bd8.zip
[WebAssembly] Add a few optimization ideas to README.txt.
llvm-svn: 269677
-rw-r--r--llvm/lib/Target/WebAssembly/README.txt15
1 files changed, 15 insertions, 0 deletions
diff --git a/llvm/lib/Target/WebAssembly/README.txt b/llvm/lib/Target/WebAssembly/README.txt
index 404ea2ade0f..7699ecc7dd0 100644
--- a/llvm/lib/Target/WebAssembly/README.txt
+++ b/llvm/lib/Target/WebAssembly/README.txt
@@ -113,3 +113,18 @@ particularly when duplicating code, to allow register coloring to be aware of
the duplication.
//===---------------------------------------------------------------------===//
+
+WebAssemblyRegStackify could use AliasAnalysis to reorder loads and stores more
+aggressively.
+
+//===---------------------------------------------------------------------===//
+
+WebAssemblyRegStackify is currently a greedy algorithm. This means that, for
+example, a binary operator will stackify with its user before its operands.
+However, if moving the binary operator to its user moves it to a place where
+its operands can't be moved to, it would be better to leave it in place, or
+perhaps move it up, so that it can stackify its operands. A binary operator
+has two operands and one result, so in such cases there could be a net win by
+prefering the operands.
+
+//===---------------------------------------------------------------------===//
OpenPOWER on IntegriCloud