public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andi Kleen <ak@suse.de>
Cc: Keith Owens <kaos@ocs.com.au>,
	linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: module compiler version check still needed?
Date: Mon, 14 Aug 2006 00:04:33 +0200	[thread overview]
Message-ID: <20060813220433.GS3543@stusta.de> (raw)
In-Reply-To: <200608132227.24719.ak@suse.de>

On Sun, Aug 13, 2006 at 10:27:24PM +0200, Andi Kleen wrote:
> On Sunday 13 August 2006 06:59, Keith Owens wrote:
> > Andi Kleen (on Sun, 13 Aug 2006 06:48:36 +0200) wrote:
> > >
> > >Does anybody know of any reason why we would still need the compiler version
> > >check during module loading? AFAIK on i386 it was only needed to handle
> > >2.95 (which got dropped) and on x86-64 it was never needed. Is there
> > >a need on any other architecture for it?
> > 
> > IA64 still needs the check.  include/asm-ia64/spinlock.h generates
> > different calls to the out of line spinlock handler, depending on the
> > version of gcc.
> 
> Thanks. But I guess it could be used to MODULE_ARCH_VERMAGIC for ia64 only then.
> If nobody else complains I will do that.

People might not complain until this is for some time in a released 
kernel.

Why don't you check yourself?

  grep -r __GNUC__ *
  grep -r cc-version *

There are over 100 results, but it's easy to spot the few requiring a 
deeper look.

> -Andi

cu
Adrian

-- 

    Gentoo kernels are 42 times more popular than SUSE kernels among
    KLive users  (a service by SUSE contractor Andrea Arcangeli that
    gathers data about kernels from many users worldwide).

       There are three kinds of lies: Lies, Damn Lies, and Statistics.
                                                    Benjamin Disraeli


  reply	other threads:[~2006-08-13 22:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-13  4:48 module compiler version check still needed? Andi Kleen
2006-08-13  4:59 ` Keith Owens
2006-08-13 20:27   ` Andi Kleen
2006-08-13 22:04     ` Adrian Bunk [this message]
2006-08-13 22:14     ` Matthew Wilcox
2006-08-14  4:59       ` Andi Kleen
2006-08-14  5:38         ` Sam Ravnborg
2006-08-14  5:45           ` Andi Kleen
2006-08-14  9:06 ` Arjan van de Ven
2006-08-14  9:19   ` Andi Kleen
2006-08-14 22:11     ` Adrian Bunk

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=20060813220433.GS3543@stusta.de \
    --to=bunk@stusta.de \
    --cc=ak@suse.de \
    --cc=kaos@ocs.com.au \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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