From: Nick Desaulniers <ndesaulniers@google.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: kernel test robot <lkp@intel.com>,
kbuild-all@lists.01.org,
clang-built-linux <clang-built-linux@googlegroups.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Thomas Gleixner <tglx@linutronix.de>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [linux-next:master 5868/6773] arch/powerpc/mm/mem.c:91:12: warning: no previous prototype for function 'create_section_mapping'
Date: Wed, 18 Nov 2020 14:32:42 -0800 [thread overview]
Message-ID: <CAKwvOdkLpCL22beGLwVJOYiHkF7zJE2AX2OB_FJmQE36WNgj0g@mail.gmail.com> (raw)
In-Reply-To: <CAPcyv4haEaWN9f6eCpnQEcjo4kcGwYp8dcs2PLDnvhG6wj8cDw@mail.gmail.com>
On Wed, Nov 18, 2020 at 11:22 AM Dan Williams <dan.j.williams@intel.com> wrote:
>
> I do not see these errors with gcc.
>
> I feel like clang errors should be flagged / de-emphasized when the
> same error does not appear on gcc.
Also, note that Clang has warnings GCC does not, and vice versa (I
imagine a Venn Diagram). I give you the benefit of the doubt to mean
"warnings that both compilers support, but only one is emitting for
whatever reason" which is fair; though warnings unique to one compiler
can be a competitive advantage.
--
Thanks,
~Nick Desaulniers
prev parent reply other threads:[~2020-11-18 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 12:26 kernel test robot
2020-11-18 19:22 ` Dan Williams
2020-11-18 19:52 ` Nick Desaulniers
2020-11-18 21:19 ` Randy Dunlap
2020-11-18 21:38 ` Dan Williams
2020-11-18 22:48 ` Randy Dunlap
2020-11-18 22:32 ` Nick Desaulniers [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=CAKwvOdkLpCL22beGLwVJOYiHkF7zJE2AX2OB_FJmQE36WNgj0g@mail.gmail.com \
--to=ndesaulniers@google.com \
--cc=akpm@linux-foundation.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=tglx@linutronix.de \
/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