From: Borislav Petkov <bp@alien8.de>
To: Chris Frey <cdfrey@foursquare.net>
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: compiler warnings in 2.6.35.2
Date: Tue, 17 Aug 2010 18:20:52 +0200 [thread overview]
Message-ID: <20100817162052.GA12785@a1.tnic> (raw)
In-Reply-To: <20100817155333.GA17624@foursquare.net>
From: Chris Frey <cdfrey@foursquare.net>
Date: Tue, Aug 17, 2010 at 11:53:33AM -0400
> > > > > CC mm/swap.o
> > > > > In file included from include/linux/kobject.h:21,
> > > > > from include/linux/sched.h:91,
> > > > > from mm/swap.c:17:
> > > > > include/linux/sysfs.h:183: warning: parameter has incomplete type
> > > > > /home/cdfrey/kernel/git/linux/arch/x86/include/asm/cpufeature.h: In function `__static_cpu_has':
> > > > > /home/cdfrey/kernel/git/linux/arch/x86/include/asm/cpufeature.h:315: warning: asm operand 1 probably doesn't match constraints
> > > >
> > > > Which compiler version are you using?
> > >
> > > GCC 3.3
> >
> > Any chance to upgrade to a 4.x version?
>
> I could, but Documentation/Changes says gcc 3.2 is the minimum, so I hoped
> 3.3 would be sufficient.
This is actually something we're looking to change now:
http://lkml.indiana.edu/hypermail/linux/kernel/1005.2/01239.html
@hpa: there are some gcc3.x users left, obviously.
>
> As for the first warning, doesn't it just need include/linux/kobject.h
> to be included for the enum type?
This is a gcc 3.x problem AFAIK.
> As for the second warning, I'm not sure I even understand it.
Ditto.
So why do you want to stay with 3.x anyway?
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2010-08-17 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 2:12 compiler warnings in 2.6.35.2 Chris Frey
2010-08-17 5:34 ` Borislav Petkov
2010-08-17 6:28 ` Chris Frey
2010-08-17 6:31 ` Borislav Petkov
2010-08-17 15:53 ` Chris Frey
2010-08-17 16:20 ` Borislav Petkov [this message]
2010-08-17 17:15 ` Anca Emanuel
2010-08-17 18:45 ` Borislav Petkov
2010-08-17 19:09 ` Anca Emanuel
2010-08-18 13:36 ` Greg KH
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=20100817162052.GA12785@a1.tnic \
--to=bp@alien8.de \
--cc=cdfrey@foursquare.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@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