From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Christopher Li <sparse@chrisli.org>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 4/8] dump-ir: set the default optimization level to 2
Date: Fri, 15 Sep 2017 09:40:30 +0200 [thread overview]
Message-ID: <20170915074034.7785-5-luc.vanoostenryck@gmail.com> (raw)
In-Reply-To: <20170915074034.7785-1-luc.vanoostenryck@gmail.com>
Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
---
lib.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lib.c b/lib.c
index a78926dfd..6f8ee1e59 100644
--- a/lib.c
+++ b/lib.c
@@ -45,7 +45,9 @@
#include "target.h"
#include "version.h"
-int verbose, optimize, optimize_size, preprocessing;
+int verbose, preprocessing;
+int optimize = 2;
+int optimize_size = 0;
int die_if_error = 0;
int has_error = 0;
--
2.14.0
next prev parent reply other threads:[~2017-09-15 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 7:40 [PATCH 0/8] dump the IR Luc Van Oostenryck
2017-09-15 7:40 ` [PATCH 1/8] dump-ir: add defines for the compilation passes Luc Van Oostenryck
2017-09-15 7:40 ` [PATCH 2/8] dump-ir: allow to specify the passes to execute via cli's options Luc Van Oostenryck
2017-09-15 7:40 ` [PATCH 3/8] dump-ir: activate/deactive pass 'mem2reg' Luc Van Oostenryck
2017-09-15 7:40 ` Luc Van Oostenryck [this message]
2017-09-15 7:40 ` [PATCH 5/8] dump-ir: use -O0 Luc Van Oostenryck
2017-09-15 7:40 ` [PATCH 6/8] dump-ir: saner use of fdump_linearize Luc Van Oostenryck
2017-09-15 7:40 ` [PATCH 7/8] dump-ir: rename -fdump-linearize to -fdump-ir Luc Van Oostenryck
2017-09-15 7:40 ` [PATCH 8/8] dump-ir: make it more flexible Luc Van Oostenryck
2017-09-15 17:06 ` [PATCH 0/8] dump the IR Christopher Li
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=20170915074034.7785-5-luc.vanoostenryck@gmail.com \
--to=luc.vanoostenryck@gmail.com \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.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).