public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	Axel Reinhold <axel@freakout.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
Date: Mon, 6 Aug 2007 23:16:31 +0200	[thread overview]
Message-ID: <20070806211631.GA14501@1wt.eu> (raw)
In-Reply-To: <ebf06e6c083df46dabc15454dcd89362@kernel.crashing.org>

On Mon, Aug 06, 2007 at 11:15:08PM +0200, Segher Boessenkool wrote:
> >Well, top-level assembly is usually nasty.  Setting the section in the
> >assembly statement as you said is probably the only thing you *can* do.
> 
> You'll probably need to (at the end of the asm block) restore
> the current section to what it was before (".previous"), too.

Didn't know about this one, thanks for the hint !

> >I don't think there is any requirement that top-level assembly
> >statements get the section set to .text on their behalf.
> 
> Correct.
> 
> 
> Segher

Regards,
Willy


  reply	other threads:[~2007-08-06 21:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-05  8:56 Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3 Axel Reinhold
2007-08-05  9:49 ` Willy Tarreau
2007-08-05 15:43 ` Willy Tarreau
2007-08-05 19:17   ` Willy Tarreau
2007-08-06 13:05   ` Segher Boessenkool
2007-08-06 13:26     ` Willy Tarreau
2007-08-06 17:39       ` H. Peter Anvin
2007-08-06 17:45         ` Willy Tarreau
2007-08-06 18:01           ` H. Peter Anvin
2007-08-06 19:13             ` Willy Tarreau
2007-08-06 21:15             ` Segher Boessenkool
2007-08-06 21:16               ` Willy Tarreau [this message]
2007-08-07  5:04                 ` Axel Reinhold
2007-08-07  8:12                   ` Willy Tarreau

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=20070806211631.GA14501@1wt.eu \
    --to=w@1wt.eu \
    --cc=axel@freakout.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=segher@kernel.crashing.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