From: Peter Zijlstra <peterz@infradead.org>
To: Qian Cai <cai@lca.pw>
Cc: mingo@redhat.com, valentin.schneider@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched/core: silence a warning in sched_init()
Date: Tue, 25 Jun 2019 17:57:45 +0200 [thread overview]
Message-ID: <20190625155745.GF3419@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1561475229.5154.74.camel@lca.pw>
On Tue, Jun 25, 2019 at 11:07:09AM -0400, Qian Cai wrote:
> On Tue, 2019-06-25 at 16:25 +0200, Peter Zijlstra wrote:
> > On Tue, Jun 25, 2019 at 10:04:19AM -0400, Qian Cai wrote:
> > > On Tue, 2019-06-25 at 15:52 +0200, Peter Zijlstra wrote:
> > > Yes, -Wmissing-prototype makes no sense, but "-Wunused-but-set-variable" is
> > > pretty valid to catch certain developer errors. For example,
> > >
> > > https://lists.linuxfoundation.org/pipermail/iommu/2019-May/035680.html
> > >
> > > >
> > > > As to this one, ideally the compiler would not be stupid, and understand
> > > > the below, but alas.
> > >
> > > Pretty sure that won't work, as the compiler will complain something like,
> > >
> > > ISO C90 forbids mixed declarations and code
> >
> > No, it builds just fine, it's a new block and C allows new variables at
> > every block start -- with the scope of that block.
>
> I remember I tried that before but recalled the error code wrong. Here it is,
>
> kernel/sched/core.c:5940:17: warning: unused variable 'ptr' [-Wunused-variable]
> unsigned long ptr = (unsigned long)kzalloc(alloc_size,
> GFP_NOWAIT);
Yes, I know, I tried. And GCC is a moron because of it.
next prev parent reply other threads:[~2019-06-25 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 12:44 [PATCH v2] sched/core: silence a warning in sched_init() Qian Cai
2019-06-25 13:52 ` Peter Zijlstra
2019-06-25 14:04 ` Qian Cai
2019-06-25 14:25 ` Peter Zijlstra
2019-06-25 15:07 ` Qian Cai
2019-06-25 15:57 ` Peter Zijlstra [this message]
2019-07-18 20:44 ` Qian Cai
2019-07-08 14:32 ` Qian Cai
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=20190625155745.GF3419@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cai@lca.pw \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=valentin.schneider@arm.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.