public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Doug Ledford <dledford@redhat.com>,
	Linux-Next Mailing List <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Bart Van Assche <bart.vanassche@wdc.com>
Subject: Re: linux-next: build warnings after merge of the rdma tree
Date: Tue, 10 Jul 2018 14:05:12 +1000	[thread overview]
Message-ID: <20180710140512.53d67d40@canb.auug.org.au> (raw)
In-Reply-To: <20180710034157.GA17400@mellanox.com>

[-- Attachment #1: Type: text/plain, Size: 595 bytes --]

Hi Jason,

On Mon, 9 Jul 2018 21:41:57 -0600 Jason Gunthorpe <jgg@mellanox.com> wrote:
> 
> What compiler is producing these? I got nothing from 0-day build
> service or my local gcc-7..

The x86 compiler is a v7.3.1 cross compiler hosted on PowerPC LE and
built from sources.

> They are false positives and I guess we need to put the
> uninitialized_var back that was hiding them.

Rats.  :-(

> Also curious that the powerpc compiler gets a different set..

The powerpc builds are done with:

$ gcc --version
gcc (Debian 7.3.0-21) 7.3.0

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2018-07-10  4:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-10  1:33 linux-next: build warnings after merge of the rdma tree Stephen Rothwell
2018-07-10  3:41 ` Jason Gunthorpe
2018-07-10  4:05   ` Stephen Rothwell [this message]
2018-07-10  4:11     ` Jason Gunthorpe

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=20180710140512.53d67d40@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=bart.vanassche@wdc.com \
    --cc=dledford@redhat.com \
    --cc=jgg@mellanox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /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