All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Jan Beulich <JBeulich@novell.com>,
	sedat.dilek@gmail.com, Alan Modra <amodra@bigpond.net.au>,
	Ingo Molnar <mingo@elte.hu>, "H.J. Lu" <hjl.tools@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	binutils <binutils@sourceware.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: PATCH: Add --size-check=[error|warning]
Date: Mon, 14 Mar 2011 15:24:45 -0400	[thread overview]
Message-ID: <20110314192445.GD20259@home.goodmis.org> (raw)
In-Reply-To: <4D7E4338.1060302@zytor.com>

On Mon, Mar 14, 2011 at 09:32:56AM -0700, H. Peter Anvin wrote:
> On 03/14/2011 04:26 AM, Jan Beulich wrote:
> > 
> > Making the kernel build system check for certain newly introduced
> > gas options would again require changes to the kernel sources,
> > which is precisely what is impossible to do for past kernel releases
> > (and bisection in particular).
> > 
> 
> But something like "make CC='gcc -Wa,--size-check=warning'" should work,
> I believe (tweaking may be required, but that's the idea).  Passing an
> option to the assembler is a helluva lot easier than redirecting to a
> different assembler.
> 
> 	-hpa
> 

Even if the above does work, how do we go about educating users doing
bisects with latest binutils? This is a very common practice among
kernel developers with users that hit bugs. And right now there's just a
handful of people that know of this work-around.

It will become a huge burden to us and our users (which is everyone
using Linux), if we do not understand the reason a build breaks when
doing a bisect, just because some "bug" in asm which binutils use to
work with now errors on.

If it was a bug in asm, but binutils can cope with it, then it should be
a warning. If binutils can't cope, then error.

-- Steve


  reply	other threads:[~2011-03-14 19:24 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 [this message]
2011-03-14 19:58       ` Linus Torvalds
2011-03-14 12:56 ` Ingo Molnar
     [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=20110314192445.GD20259@home.goodmis.org \
    --to=rostedt@goodmis.org \
    --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=mingo@elte.hu \
    --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 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.