mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Eric Vlette <eric.valette@free.fr>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Typo in linux-2.6.38/arch/x86/kernel/entry_32.S
Date: Wed, 16 Mar 2011 16:22:34 -0400	[thread overview]
Message-ID: <1300306954.16880.51.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <4D8118F7.5060107@free.fr>

On Wed, 2011-03-16 at 21:09 +0100, Eric Vlette wrote:
> On 16/03/2011 20:52, Steven Rostedt wrote:
> > On Wed, Mar 16, 2011 at 02:15:26PM +0100, Eric Valette wrote:
> >> Hi,
> >>
> >> Trying to compile 2.6.38, I found the follwoing bug. Compiler barks...
> > 
> > New compiler? (new binutils more likely)
> 
> Maybe. I use debian unstable + experimental and upgrade packages almost
> everyday...

You probably have new binutils.

What does "as --version" give you. Binutils 2.21... ?

I think it was 2.21 that started giving problems.

> 
> >>
> >> diff linux-2.6.38/arch/x86/kernel/entry_32.S
> >> linux-2.6.38/arch/x86/kernel/entry_32.S~
> >> 1416c1416
> >> < END(async_page_fault)
> >> ---
> >>> END(apf_page_fault)
> 
> But obviously the begin end is not symmetric as in other function.

Right, there was a discussion before about this causing issues with new
binutils, and I think Ingo or Thomas said that they had patches to fix
these for x86. Which this looks like one.

The old binutils never complained.

-- Steve



  reply	other threads:[~2011-03-16 20:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-16 13:15 Eric Valette
2011-03-16 19:52 ` Steven Rostedt
2011-03-16 20:09   ` Eric Vlette
2011-03-16 20:22     ` Steven Rostedt [this message]
2011-03-16 20:32       ` Eric Valette
2011-03-16 20:44         ` Steven Rostedt
2011-03-16 20:53           ` Eric Valette
2011-03-17  8:31             ` 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=1300306954.16880.51.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=eric.valette@free.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®