From: Ingo Molnar <mingo@elte.hu>
To: sedat.dilek@gmail.com
Cc: Jan Beulich <JBeulich@novell.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
Alan Modra <amodra@bigpond.net.au>,
binutils <binutils@sourceware.org>,
LKML <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PATCH: Add --size-check=[error|warning]
Date: Mon, 14 Mar 2011 13:56:46 +0100 [thread overview]
Message-ID: <20110314125646.GA28851@elte.hu> (raw)
In-Reply-To: <AANLkTinDTyupNgZR-0izCWrpwOnE1wEcubn+M3o=Mgy2@mail.gmail.com>
* Sedat Dilek <sedat.dilek@googlemail.com> wrote:
> Nice to see there is an offer for a fix from binutils-side.
Agreed.
> That's why I am on linux-next to squash bugs, not to ignore "warnings"
We x86 arch maintainers definitely do not ignore warnings from the assembler.
Assembler warnings were pretty good historically and seldom produce false positives.
> BTW "warnings", did someone tried gcc-4.6? I used a snapshot from mid February
> (from Debian/experimental): My linux-next build-log and the amount of warnings
> doubled or even more (unfortunately, I have thrown away that logs and binaries).
> Are all of these warnings ignoreable? Which of them are really severe?
Most of those are -Wunused-but-set-variable warnings, right? I'm definitely not
ignoring the ones that affect the code i maintain - so they are very much useful.
But if GCC broke the build unnecessarily, just to over-eagerly warn about something
that worked fine before, that would be extremely counter-productive! In such a
situation the Linux kernel project would likely be fed up enough to build its own
sane compiler/assembler/linker combo and would aim to become entirely independent in
terms of its build environment.
Thanks,
Ingo
next prev parent reply other threads:[~2011-03-14 12:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 11:02 PATCH: Add --size-check=[error|warning] Sedat Dilek
2011-03-14 11:26 ` Jan Beulich
2011-03-14 11:35 ` Ingo Molnar
2011-03-14 11:38 ` Sedat Dilek
2011-03-14 11:52 ` Sedat Dilek
2011-03-14 12:21 ` Jan Beulich
2011-03-14 12:38 ` Sedat Dilek
2011-03-14 12:51 ` Sedat Dilek
2011-03-14 15:56 ` Ian Lance Taylor
2011-03-14 18:01 ` H. Peter Anvin
2011-03-14 16:32 ` H. Peter Anvin
2011-03-14 19:24 ` Steven Rostedt
2011-03-14 19:58 ` Linus Torvalds
2011-03-14 12:56 ` Ingo Molnar [this message]
[not found] <20110311165802.GA3508@intel.com>
[not found] ` <4D7A64670200007800035F4C@vpn.id2.novell.com>
[not found] ` <AANLkTikG8wa1Em0bEUddbYpYs2TzFFTDb95qWFJ3xSbv@mail.gmail.com>
[not found] ` <4D7DE39302000078000362E6@vpn.id2.novell.com>
2011-03-14 9:55 ` Ingo Molnar
2011-03-14 10:41 ` Alan Modra
2011-03-14 10:50 ` Pekka Enberg
2011-03-14 18:03 ` Alan Cox
2011-03-14 10:52 ` Jan Beulich
[not found] ` <AANLkTi=3AiLaw5Gnis8Ha4eRXirk0s-Cnk2zzN12YDpH__45869.1711457961$1300099861$gmane$org@mail.gmail.com>
2011-03-14 11:02 ` Andreas Schwab
2011-03-14 11:12 ` Pekka Enberg
2011-03-14 12:02 ` Andreas Schwab
2011-03-14 12:13 ` Ingo Molnar
2011-03-14 12:55 ` Andreas Schwab
2011-03-14 13:17 ` Ingo Molnar
2011-03-14 13:43 ` Andreas Schwab
2011-03-14 12:10 ` Ingo Molnar
2011-03-14 12:23 ` Ingo Molnar
2011-03-14 12:25 ` Ingo Molnar
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=20110314125646.GA28851@elte.hu \
--to=mingo@elte.hu \
--cc=JBeulich@novell.com \
--cc=akpm@linux-foundation.org \
--cc=amodra@bigpond.net.au \
--cc=binutils@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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