All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH] update TODOs
Date: Wed, 14 Oct 2020 00:16:36 +0200	[thread overview]
Message-ID: <20201013221636.7664-1-luc.vanoostenryck@gmail.com> (raw)

A few things are now done: remove them from the TODO.
A few things need to be done: add them to the TODO.

Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
 Documentation/TODO.md | 29 +++++++++++++++++++++--------
 1 file changed, 21 insertions(+), 8 deletions(-)

diff --git a/Documentation/TODO.md b/Documentation/TODO.md
index e2043e481f99..4dc9e63ab207 100644
--- a/Documentation/TODO.md
+++ b/Documentation/TODO.md
@@ -4,13 +4,13 @@ TODO
 Essential
 ---------
 * SSA is broken by simplify_loads() & branches rewriting/simplification
-* attributes of struct, union & enums are ignored (and possibly in other
-  cases too).
-* add support for bitwise enums
+* attributes of struct, union & enums are ignored (and maybe others too).
+  This requires correct support for __packed which itself needs partial
+  and unaligned loads & stores (wip)
+* add support for bitwise enums (wip)
 
 Documentation
 -------------
-* document the extensions
 * document the API
 * document the limitations of modifying ptrlists during list walking
 * document the data structures
@@ -27,7 +27,7 @@ Core
 
 Testsuite
 ---------
-* there are more than 50 failing tests. They should be fixed
+* there are 60 failing tests. They should be fixed
   (but most are non-trivial to fix).
 
 Misc
@@ -36,15 +36,26 @@ Misc
 * parse __attribute_((fallthrough))
 * add support for format(printf())  (WIP by Ben Dooks)
 * make use of UNDEFs (issues warnings, simplification, ... ?)
-* add a pass to inline small functions during simplification.
+* make memory accesses more explicit: add EXPR_ACCESS (wip)
+* it would be nice to do our own parsing of floating point (wip)
+* some header files needed for crypto/ need __vector or __fp16
+* some even need __complex
 
 Optimization
 ------------
+* a lot of small simplifications are waiting to be upstreamed
+* the domtree need to be rebuilt (or updated)
+* critical edges need to be split
 * the current way of doing CSE uses a lot of time
 * add SSA based DCE
 * add SSA based PRE
 * Add SSA based SCCP
+* add a pass to inline small functions during simplification.
 * use better/more systematic use of internal verification framework
+* tracking of operands size should be improved (WIP)
+* OP_INLINE is sometimes in the way
+* would be nice to strictly separate phases that don't changes the
+  CFG and thus the dominance tree.
 
 IR
 --
@@ -60,13 +71,15 @@ LLVM
 
 Internal backends
 -----------------
-* add some basic register allocation
+* it would be nice the upstream the code generator
 * add a pass to transform 3-addresses code to 2-addresses
+* add some basic register allocation
+* add a pass to order the BBs and changes 2-ways CBR into one-way branches
 * what can be done for x86?
+* add support to add constraints in the MD rules
 
 Longer term/to investigate
 --------------------------
-* better architecture handling than current machine.h + target.c
 * attributes are represented as ctypes's alignment, modifiers & contexts
   but plenty of attributes doesn't fit, for example they need arguments.
   * format(printf, ...),
-- 
2.28.0


                 reply	other threads:[~2020-10-14  9:23 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201013221636.7664-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.