From: willy@linux.intel.com (Matthew Wilcox)
Subject: [PATCH v2] NVMe: silence GCC warning on 32 bit
Date: Mon, 24 Mar 2014 09:31:54 -0400 [thread overview]
Message-ID: <20140324133154.GD5777@linux.intel.com> (raw)
In-Reply-To: <20140324131104.GC5777@linux.intel.com>
On Mon, Mar 24, 2014@09:11:04AM -0400, Matthew Wilcox wrote:
> On Tue, Mar 04, 2014@10:36:07AM +0100, Paul Bolle wrote:
> > Also note that it's actually not clear to me why these warnings only
> > trigger on 32 bit. I guess there's some int/long conversion lurking
> > somewhere. I haven't found it.
>
> I bet you're using a different revision of the compiler on 32 and 64 bit.
> Different gcc revisions have different abilities to track initialisation.
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 :-(
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <willy@linux.intel.com>
To: Paul Bolle <pebolle@tiscali.nl>
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: Mon, 24 Mar 2014 09:31:54 -0400 [thread overview]
Message-ID: <20140324133154.GD5777@linux.intel.com> (raw)
In-Reply-To: <20140324131104.GC5777@linux.intel.com>
On Mon, Mar 24, 2014 at 09:11:04AM -0400, Matthew Wilcox wrote:
> On Tue, Mar 04, 2014 at 10:36:07AM +0100, Paul Bolle wrote:
> > Also note that it's actually not clear to me why these warnings only
> > trigger on 32 bit. I guess there's some int/long conversion lurking
> > somewhere. I haven't found it.
>
> I bet you're using a different revision of the compiler on 32 and 64 bit.
> Different gcc revisions have different abilities to track initialisation.
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 :-(
next prev parent reply other threads:[~2014-03-24 13:31 UTC|newest]
Thread overview: 31+ 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-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-20 22:11 ` Paul Bolle
2014-02-21 16:37 ` Keith Busch
2014-02-21 16:37 ` Keith Busch
2014-03-04 9:36 ` [PATCH v2] " Paul Bolle
2014-03-04 9:36 ` Paul Bolle
2014-03-05 15:09 ` Keith Busch
2014-03-05 15:09 ` Keith Busch
2014-03-06 9:56 ` Paul Bolle
2014-03-06 9:56 ` Paul Bolle
2014-03-24 13:11 ` Matthew Wilcox
2014-03-24 13:11 ` Matthew Wilcox
2014-03-24 13:31 ` Matthew Wilcox [this message]
2014-03-24 13:31 ` Matthew Wilcox
2014-03-24 15:36 ` Paul Bolle
2014-03-24 15:36 ` Paul Bolle
2014-03-24 15:49 ` Geert Uytterhoeven
2014-03-24 15:49 ` Geert Uytterhoeven
2014-03-24 15:57 ` Paul Bolle
2014-03-24 15:57 ` Paul Bolle
2014-05-08 7:12 ` Paul Bolle
2014-05-08 7:12 ` Paul Bolle
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=20140324133154.GD5777@linux.intel.com \
--to=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 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.