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 0/5] teach memory simplification about ASM instructions
Date: Sun, 21 Feb 2021 23:34:47 +0100	[thread overview]
Message-ID: <20210221223452.8075-1-luc.vanoostenryck@gmail.com> (raw)

This series fixes simplify_memops() which didn't took in account the
fact that ASM instructions can also modify the content of the memory:
either because it contains an output memory operand, or because
it explicetly clobbers memory in some other way.

Luc Van Oostenryck (5):
  reorg dominates()
  asm-mem: add testcase for missing reload after asm memops
  asm-mem: does it clobber memory?
  asm-mem: does it output to memory?
  asm-mem: teach dominates() about OP_ASM

 flow.c                           | 17 +++++++++++++----
 linearize.c                      |  9 ++++++++-
 linearize.h                      |  2 ++
 validation/mem2reg/asm-reload0.c | 14 ++++++++++++++
 4 files changed, 37 insertions(+), 5 deletions(-)
 create mode 100644 validation/mem2reg/asm-reload0.c


base-commit: 2494587e823700458923052b17b0b981be92d776
-- 
2.30.0


             reply	other threads:[~2021-02-21 22:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 22:34 Luc Van Oostenryck [this message]
2021-02-21 22:34 ` [PATCH 1/5] reorg dominates() Luc Van Oostenryck
2021-02-21 22:34 ` [PATCH 2/5] asm-mem: add testcase for missing reload after asm memops Luc Van Oostenryck
2021-02-21 22:34 ` [PATCH 3/5] asm-mem: does it clobber memory? Luc Van Oostenryck
2021-02-21 22:34 ` [PATCH 4/5] asm-mem: does it output to memory? Luc Van Oostenryck
2021-02-21 22:34 ` [PATCH 5/5] asm-mem: teach dominates() about OP_ASM Luc Van Oostenryck

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=20210221223452.8075-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.