mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Nathan Chancellor <natechancellor@gmail.com>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>, Peter Zijlstra <peterz@infradead.org>
Subject: Re: x86 - clang / objtool status
Date: Fri, 19 Jul 2019 08:44:22 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1907190812040.1785@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAKwvOdkYKweg5A6jwomPUjjkRWq5=oVMVM=Wcg=ho+crOnr3Ew@mail.gmail.com>

On Thu, 18 Jul 2019, Nick Desaulniers wrote:
> On Thu, Jul 18, 2019 at 1:40 PM Thomas Gleixner <tglx@linutronix.de> wrote:
> > after picking up Josh's objtool updates I gave clang a test ride again.
> 
> Thanks for testing and the reports; these are valuable and we
> appreciate the help debugging them.
> 
> > 2) debian distro config
> 
> Is this checked into the tree, or where can I find it?

See below.

> >   drivers/gpu/drm/radeon/evergreen_cs.o: warning: objtool: evergreen_cs_parse() falls through to next function evergreen_dma_cs_parse()
> 
> fall through warnings look new to me, but Linaro's KernelCI is
> currently screaming with tons of reports of -Wfallthrough throughout
> the kernel.  I assume they're related?

I don't think so. The compiler does not warn about a missing fallthrough.

> > 3) allmodconfig:
> >
> >   drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool: .altinstr_replacement+0x56: redundant UACCESS disable
> 
> Do you still have these object files laying around? Josh asked for
> them in a new thread (from the previous thread), not sure if it's ok
> to attach object files to emails to LKML? (html email is not allowed,
> are binary attachments?)

I've uploaded the configs and object files to:

     https://tglx.de/~tglx/clang.tar.bz2

contains:

clang/
clang/debian/
clang/debian/atom.o
clang/debian/platform.o
clang/debian/i915_gem_execbuffer.o
clang/debian/.config
clang/debian/evergreen_cs.o
clang/allmod/
clang/allmod/ubsan.o
clang/allmod/i915_gem_execbuffer.o
clang/allmod/.config
clang/allmod/sata_dwc_460ex.o
clang/allmod/common.o
clang/allmod/signal.o
clang/allmod/ia32_signal.o

i.e. the .config and the offending object files for the debian and
allmodconfig builds.

Thanks,

	tglx



  reply	other threads:[~2019-07-19  6:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 20:40 Thomas Gleixner
2019-07-18 20:58 ` Nathan Chancellor
2019-07-19  6:39   ` Thomas Gleixner
2019-07-19  7:00     ` Arnd Bergmann
2019-07-19  7:03     ` Nathan Chancellor
2019-07-24 16:57     ` Nick Desaulniers
2019-07-18 22:42 ` Nick Desaulniers
2019-07-19  6:44   ` Thomas Gleixner [this message]
2019-07-19 11:37 ` Sedat Dilek
2019-07-19 13:48   ` Sedat Dilek
2019-07-22 15:40     ` Sedat Dilek
2019-07-25  6:17       ` Sedat Dilek
2019-07-24  2:43 ` Josh Poimboeuf
2019-07-24  7:47   ` Peter Zijlstra
2019-07-24 12:37     ` Josh Poimboeuf
2019-07-24 12:55     ` Josh Poimboeuf
2019-07-24 13:35       ` Peter Zijlstra
2019-07-24 14:05         ` Josh Poimboeuf
2019-07-24 14:10         ` Peter Zijlstra
2019-07-24 16:48           ` [PATCH] objtool: Improve UACCESS coverage Peter Zijlstra
2019-07-24 16:54             ` Nathan Chancellor
2019-07-24 16:55             ` Nick Desaulniers
2019-07-24 18:30             ` Sedat Dilek
2019-07-24 18:32               ` Sedat Dilek
2019-07-24 16:52   ` x86 - clang / objtool status Peter Zijlstra
2019-07-24 17:22   ` Nick Desaulniers

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=alpine.DEB.2.21.1907190812040.1785@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --cc=clang-built-linux@googlegroups.com \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.org \
    --cc=x86@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®