From: Andi Kleen <ak@suse.de>
To: Martin Bligh <mbligh@google.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: x86_64 compile spewing hundreds of warnings - started 2.6.15-git8
Date: Mon, 31 Jul 2006 22:19:04 +0200 [thread overview]
Message-ID: <200607312219.04303.ak@suse.de> (raw)
In-Reply-To: <44CE2C61.4010809@google.com>
On Monday 31 July 2006 18:14, Martin Bligh wrote:
> Martin Bligh wrote:
> > between 2.6.15-git7 and 2.6.15-git8 we started getting hundreds of
> > compile warnings:
> >
> > -git7: http://test.kernel.org/20295/debug/test.log.0
> > -git8: http://test.kernel.org/20402/debug/test.log.0
> >
> > Warnings look like this:
> >
> > include/asm/bitops.h: In function `load_elf32_binary':
> > include/asm/bitops.h:30: warning: read-write constraint does not allow a
> > register
Hmm, as far as I can see I do the same as i386 with these constraints.
Are you sure i386 doesn't warn either?
-Andi
prev parent reply other threads:[~2006-07-31 20:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 19:35 x86_64 compile spewing hundreds of warnings - started 2.6.15-git8 Martin Bligh
2006-03-02 19:49 ` Andi Kleen
2006-07-31 16:14 ` Martin Bligh
2006-07-31 20:19 ` Andi Kleen [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=200607312219.04303.ak@suse.de \
--to=ak@suse.de \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.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