mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Alexander van Heukelum <heukelum@fastmail.fm>
Cc: Andi Kleen <andi@firstfloor.org>,
	Alexander van Heukelum <heukelum@mailshack.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: always_inline wrapper for x86's test_bit
Date: Mon, 14 Apr 2008 14:34:57 +0200	[thread overview]
Message-ID: <20080414123457.GC18662@one.firstfloor.org> (raw)
In-Reply-To: <1208175845.22460.1247749229@webmail.messagingengine.com>

> Checked with a stock 3.2.3 form gcc.gnu.org (compiled using debian's
> gcc-2.95). It gets it right: places that should get the C version get
> the C version and places that should get the inline-assembly version
> get the inline-assembly version. No funny things at all.

Great. Thanks for testing. Perhaps the problem was limited to 2.9x only.

> B.T.W., debian and ubuntu don't provide gcc-3.2 packages. Is there a
> good reason why gcc-3.2.3 (5 years old in a week) should still be
> supported?

The compiler version is normally only moved up when there is some 
bug in an older version that cannot be reasonably be worked around.
So far 3.2 didn't have anything like this, at least not on x86
(on some other architectures there are problems with older toolkits) 

-Andi

  parent reply	other threads:[~2008-04-14 12:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-13 11:23 Alexander van Heukelum
2008-04-13 16:58 ` Andi Kleen
2008-04-13 18:03   ` Alexander van Heukelum
2008-04-13 18:16     ` Andi Kleen
2008-04-14 12:24       ` Alexander van Heukelum
2008-04-14 12:28         ` Ingo Molnar
2008-04-14 12:34         ` Andi Kleen [this message]
2008-04-14  7:52 ` Ingo Molnar
2008-04-14 13:49   ` Alexander van Heukelum

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=20080414123457.GC18662@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=heukelum@fastmail.fm \
    --cc=heukelum@mailshack.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

Powered by JetHome