public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Matthew Wilcox <willy@linux.intel.com>
Cc: Keith Busch <keith.busch@intel.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH v2] NVMe: silence GCC warning on 32 bit
Date: Thu, 08 May 2014 09:12:51 +0200	[thread overview]
Message-ID: <1399533171.19191.8.camel@x41> (raw)
In-Reply-To: <1395675399.6440.14.camel@x220>

Matthew,

Paul Bolle schreef op ma 24-03-2014 om 16:36 [+0100]:
> On Mon, 2014-03-24 at 09:31 -0400, Matthew Wilcox wrote:
> > I should try things myself before opening my big mouth.  Weird.  Using
> > gcc-4.8, I see the same thing.  Guess I should just apply the patch,
> > though it feels wrong to be initialising an entire struct just to silence
> > a bogus compiler warning :-(
> 
> I noticed this difference on a 32 bit x86 machine and a 64 bit x86
> machine that are both running Fedora 20. They both should be at
> gcc-4.8.2 for quite some time now (if I grepped the yum log correctly).
> 
> Anyhow, the warning on 32 bit is rather noisy, so I wanted it gone. But
> my comments should make clear I'm not really happy with this patch. 
> 
> And as this is now unlikely to be in time for v3.14, we might decide to
> dig deeper. It won't be the first time that a rather small change (say,
> converting a variable from signed to unsigned) turns out be enough to
> make GCC understand the flow of the code.

This noisy warning is still seen when compiling v3.15-rc4 for x86 (32
bit, that is). Assuming this patch is not queued anywhere: is the
unsophisticated approach of my v2 acceptable or would you like me to try
and find the cause of this warning?


Paul Bolle


      parent reply	other threads:[~2014-05-08  7:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18  9:02 Build regressions/improvements in v3.14-rc3 Geert Uytterhoeven
2014-02-18  9:06 ` Geert Uytterhoeven
2014-02-19  9:52 ` [PATCH] target_core_alua: silence GCC warning Paul Bolle
2014-02-19  9:59   ` Geert Uytterhoeven
2014-02-19 10:05     ` Paul Bolle
2014-02-19 22:59       ` Nicholas A. Bellinger
2014-02-20  8:07         ` [PATCH v2] " Paul Bolle
2014-02-20 18:33           ` Nicholas A. Bellinger
2014-02-20 22:11 ` [PATCH] NVMe: silence GCC warning on 32 bit Paul Bolle
2014-02-21 16:37   ` Keith Busch
2014-03-04  9:36     ` [PATCH v2] " Paul Bolle
2014-03-05 15:09       ` Keith Busch
2014-03-06  9:56         ` Paul Bolle
2014-03-24 13:11       ` Matthew Wilcox
2014-03-24 13:31         ` Matthew Wilcox
2014-03-24 15:36           ` Paul Bolle
2014-03-24 15:49             ` Geert Uytterhoeven
2014-03-24 15:57               ` Paul Bolle
2014-05-08  7:12             ` Paul Bolle [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=1399533171.19191.8.camel@x41 \
    --to=pebolle@tiscali.nl \
    --cc=geert@linux-m68k.org \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=willy@linux.intel.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