From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 5/9] dump-ir: use -O0
Date: Wed, 8 Nov 2017 11:27:58 +0100 [thread overview]
Message-ID: <20171108102802.43987-6-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20171108102802.43987-1-luc.vanoostenryck@gmail.com>
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
linearize.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/linearize.c b/linearize.c
index 31cc94806..65a4baf96 100644
--- a/linearize.c
+++ b/linearize.c
@@ -2238,6 +2238,8 @@ static struct entrypoint *linearize_fn(struct symbol *sym, struct symbol *base_t
if (fpasses & PASS_MEM2REG)
simplify_symbol_usage(ep);
+ if (optimize == 0)
+ return ep;
repeat:
/*
* Remove trivial instructions, and try to CSE
--
2.14.0
next prev parent reply other threads:[~2017-11-08 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 10:27 [PATCH 0/9] dump IR Luc Van Oostenryck
2017-11-08 10:27 ` [PATCH 1/9] dump-ir: add defines for the compilation passes Luc Van Oostenryck
2017-11-08 10:27 ` [PATCH 2/9] dump-ir: allow to specify the passes to execute via cli's options Luc Van Oostenryck
2017-11-08 10:27 ` [PATCH 3/9] dump-ir: activate/deactive pass 'mem2reg' Luc Van Oostenryck
2017-11-08 10:27 ` [PATCH 4/9] dump-ir: set the default optimization level to 2 Luc Van Oostenryck
2017-11-08 10:27 ` Luc Van Oostenryck [this message]
2017-11-08 10:27 ` [PATCH 6/9] dump-ir: saner use of fdump_linearize Luc Van Oostenryck
2017-11-08 10:28 ` [PATCH 7/9] dump-ir: rename -fdump-linearize to -fdump-ir Luc Van Oostenryck
2017-11-08 10:28 ` [PATCH 8/9] dump-ir: make it more flexible Luc Van Oostenryck
2017-11-08 10:28 ` [PATCH 9/9] dump-ir: activate -fdump-ir=mem2reg 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=20171108102802.43987-6-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).