From: Jiri Slaby <jslaby@suse.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vegard Nossum <vegard.nossum@oracle.com>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
"Luis R . Rodriguez" <mcgrof@kernel.org>
Subject: Re: [PATCH 00/12] external array access helpers
Date: Mon, 17 Oct 2016 08:26:14 +0200 [thread overview]
Message-ID: <da901406-9b3c-3e23-468b-c582a92c00ec@suse.cz> (raw)
In-Reply-To: <20161016161400.GA19899@kroah.com>
On 10/16/2016, 06:14 PM, Greg Kroah-Hartman wrote:
> Is gcc 7.0 "stable" enough that people will start to be using it soon?
Standard suse kernel builds and boots with gcc 7 just fine. But only
with 02/12 from this series. So perhaps it's not stable enough for
production use, but at least I was about to test use-after-scope gcc 7
UBSAN thingie via syzkaller soon.
thanks,
--
js
suse labs
prev parent reply other threads:[~2016-10-17 6:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 15:16 [PATCH 00/12] external array access helpers Vegard Nossum
2016-10-16 15:16 ` [PATCH 01/12] extarray: define helpers for arrays defined in linker scripts Vegard Nossum
2016-10-17 7:04 ` Greg Kroah-Hartman
2016-10-17 8:33 ` Peter Zijlstra
2016-10-17 9:01 ` Jiri Slaby
2016-10-17 9:09 ` Peter Zijlstra
2016-10-17 11:27 ` Vegard Nossum
2016-10-17 11:45 ` Peter Zijlstra
2016-10-18 8:08 ` Vegard Nossum
2016-10-18 21:18 ` Luis R. Rodriguez
2016-10-19 8:18 ` Richard Biener
2016-10-19 9:13 ` Peter Zijlstra
2016-10-19 9:33 ` Richard Biener
2016-10-19 10:25 ` Peter Zijlstra
2016-10-19 11:11 ` Richard Biener
2016-10-19 11:31 ` Peter Zijlstra
2016-11-02 12:11 ` Markus Trippelsdorf
2016-11-02 12:14 ` Richard Biener
2016-11-02 15:02 ` Linus Torvalds
2016-10-19 7:16 ` Jiri Slaby
2016-10-16 15:16 ` [PATCH 02/12] firmware: declare {__start,__end}_builtin_fw as external array Vegard Nossum
2016-10-16 15:16 ` [PATCH 03/12] ftrace: declare __{start,stop}_mcount_loc " Vegard Nossum
2016-10-16 15:16 ` [PATCH 04/12] tracing: declare __{start,stop}_{annotated_,}branch_profile " Vegard Nossum
2016-10-16 15:16 ` [PATCH 05/12] kprobes: declare __{start,stop}_kprobe_blacklist " Vegard Nossum
2016-10-17 5:53 ` Masami Hiramatsu
2016-10-16 15:16 ` [PATCH 06/12] tracing: declare __{start,stop}_ftrace_events " Vegard Nossum
2016-10-16 15:16 ` [PATCH 07/12] tracing: declare __{start,stop}_ftrace_enum_maps " Vegard Nossum
2016-10-16 15:16 ` [PATCH 08/12] tracing: declare __trace_bprintk_fmt/__tracepoint_str as external arrays Vegard Nossum
2016-10-16 15:16 ` [PATCH 09/12] tracing: declare __{start,stop}_syscalls_metadata as external array Vegard Nossum
2016-10-16 15:16 ` [PATCH 10/12] serial_core: declare __earlycon_table{,_end} " Vegard Nossum
2016-10-16 15:16 ` [PATCH 11/12] jump_label: declare jump table " Vegard Nossum
2016-10-16 16:25 ` Peter Zijlstra
2016-10-16 16:50 ` Vegard Nossum
2016-10-16 17:44 ` Peter Zijlstra
2016-10-17 21:33 ` Steven Rostedt
2016-10-16 15:16 ` [PATCH 12/12] dynamic debug: declare " Vegard Nossum
2016-10-16 16:14 ` [PATCH 00/12] external array access helpers Greg Kroah-Hartman
2016-10-16 17:05 ` Vegard Nossum
2016-10-17 7:02 ` Greg Kroah-Hartman
2016-10-17 6:26 ` Jiri Slaby [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=da901406-9b3c-3e23-468b-c582a92c00ec@suse.cz \
--to=jslaby@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.com \
/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.