From: Michal Marek <mmarek@suse.com>
To: Peter Foley <pefoley2@pefoley.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org,
Behan Webster <behanw@converseincode.com>
Subject: Re: [PATCH v4] Fixes for compiling with clang
Date: Fri, 2 Dec 2016 13:33:39 +0100 [thread overview]
Message-ID: <d419e823-8321-94d2-6f14-eac68e007eba@suse.com> (raw)
In-Reply-To: <CAOFdcFMTQbkE4ODTmrxq2dkzkNV8PXcMD0V3UhXyL62xvhgTGA@mail.gmail.com>
On 2016-12-01 19:13, Peter Foley wrote:
> On Tue, Nov 29, 2016 at 6:22 AM, Michal Marek <mmarek@suse.com> wrote:
>> Dne 28.11.2016 v 07:44 Peter Foley napsal(a):
>> This adds new -Wno-* options also for the gcc case, is there a reason
>> for this? Also, the -Wno-missing-field-initializers option is not
>> available in some old gccs, so we would need a HOSTCC equivalent of
>> cc-disable-warning.
>>
>> Michal
>
> It appeared that the conditional was simply reversed, as
> -fno-delete-null-pointer-checks is only supported by gcc, and
> explicitly not supported by clang.
> (see https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/Makefile?id=61163efae02040f66a95c8ed17f4407951ba58fa)
> It could be that the fno-delete-null-pointer-checks option was simply
> misplaced, and the Wno-options should still be guarded by if(clang),
> would that be a better approach?
I think so. The -Wno-* options had not been present before clang support
was added. It really looks like the -fno-delete-null-pointer-checks
should not be there. Added Behan to CC.
Michal
prev parent reply other threads:[~2016-12-02 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 4:27 [PATCH] " Peter Foley
2016-11-26 6:34 ` kbuild test robot
2016-11-26 8:29 ` kbuild test robot
2016-11-26 18:02 ` [PATCH v2] " Peter Foley
2016-11-26 18:20 ` [PATCH v3] " Peter Foley
2016-11-28 6:44 ` [PATCH v4] " Peter Foley
2016-11-29 14:22 ` Michal Marek
2016-12-01 18:13 ` Peter Foley
2016-12-02 12:33 ` Michal Marek [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=d419e823-8321-94d2-6f14-eac68e007eba@suse.com \
--to=mmarek@suse.com \
--cc=behanw@converseincode.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@pefoley.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 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®