On Wed, Apr 04, 2018 at 04:53:52PM +0000, Nick Desaulniers wrote:
> (re-sending as plain text)
>
> On Wed, Apr 4, 2018 at 2:38 AM Greg KH <gre...@linuxfoundation.org> wrote:
> > There are known-bugs with building a kernel with clang right now (I
> > pointed one out a few days ago about NULL checks being deleted from the
> > clang output for no good reason, which really is scary for obvious
> > reasons).
>
> Is this the thread you are referring to?
> https://lkml.org/lkml/2018/3/27/1286
>
> It's definitely something curious that I'll need to sit down and
> investigate more. If there are other known instances, it would be good to
> let me know.
Here is another horrible work around that was needed to get clang to
stop generating invalid code, beaec533fc27 ("llist: clang: introduce
member_address_is_nonnull()") That one caused a lot of odd failures by
users, I wonder what else is lurking in that same code pattern. It's a
hard one to debug...
thanks,
greg k-h
