From: "Paul E. McKenney" <paulmck@kernel.org>
To: Marco Elver <elver@google.com>
Cc: will@kernel.org, peterz@infradead.org, bp@alien8.de,
tglx@linutronix.de, mingo@kernel.org, dvyukov@google.com,
cai@lca.pw, kasan-dev@googlegroups.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] kcsan: Re-add GCC support, and compiler flags improvements
Date: Fri, 19 Jun 2020 14:49:01 -0700 [thread overview]
Message-ID: <20200619214901.GA12084@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200619032530.GI2723@paulmck-ThinkPad-P72>
On Thu, Jun 18, 2020 at 08:25:30PM -0700, Paul E. McKenney wrote:
> On Thu, Jun 18, 2020 at 11:31:15AM +0200, Marco Elver wrote:
> > Re-add GCC as a supported compiler and clean up compiler flags.
> >
> > To use KCSAN with GCC before GCC 11 is released, the following will get
> > a stable GCC 10 and cherry-pick the patches required for KCSAN support:
> >
> > git clone git://gcc.gnu.org/git/gcc.git && cd gcc
> > git checkout -b gcc-10-for-kcsan releases/gcc-10.1.0
> > git cherry-pick \
> > 4089df8ef4a63126b0774c39b6638845244c20d2 \
> > ab2789ec507a94f1a75a6534bca51c7b39037ce0 \
> > 06712fc68dc9843d9af7c7ac10047f49d305ad76
> > ./configure --prefix <your-prefix> --enable-languages=c,c++
> > make -j$(nproc) && make install
>
> Unless there are objections, I will pull this in Friday (tomorrow)
> afternoon, Pacific Time.
Hearing no objections, queued and pushd, thank you!
Thanx, Paul
> > Marco Elver (3):
> > kcsan: Re-add GCC as a supported compiler
> > kcsan: Simplify compiler flags
> > kcsan: Disable branch tracing in core runtime
> >
> > Documentation/dev-tools/kcsan.rst | 3 ++-
> > kernel/kcsan/Makefile | 4 ++--
> > lib/Kconfig.kcsan | 3 ++-
> > scripts/Makefile.kcsan | 2 +-
> > 4 files changed, 7 insertions(+), 5 deletions(-)
> >
> > --
> > 2.27.0.290.gba653c62da-goog
> >
prev parent reply other threads:[~2020-06-19 21:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 9:31 Marco Elver
2020-06-18 9:31 ` [PATCH 1/3] kcsan: Re-add GCC as a supported compiler Marco Elver
2020-06-18 9:31 ` [PATCH 2/3] kcsan: Simplify compiler flags Marco Elver
2020-06-18 9:31 ` [PATCH 3/3] kcsan: Disable branch tracing in core runtime Marco Elver
2020-06-19 3:25 ` [PATCH 0/3] kcsan: Re-add GCC support, and compiler flags improvements Paul E. McKenney
2020-06-19 21:49 ` Paul E. McKenney [this message]
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=20200619214901.GA12084@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=bp@alien8.de \
--cc=cai@lca.pw \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=will@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
all inboxes | Powered by JetHome®