public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 5/5] fix sn rw_mmr.h to use intrinsic
Date: Tue, 31 Jan 2006 10:57:05 +0000	[thread overview]
Message-ID: <yq04q3kr7ge.fsf@jaguar.mkp.net> (raw)
In-Reply-To: <200601270137.k0R1big21236@unix-os.sc.intel.com>

>>>>> "Ken" = Chen, Kenneth W <kenneth.w.chen@intel.com> writes:

Ken> Jes Sorensen wrote on Friday, January 27, 2006 1:57 AM
>>  I'll have to test this. However it really doesn't matter much as
>> we won't be building the SN kernel with ICC.

Ken> When I build a generic kernel, all sn code are pulled in and need
Ken> to be compiled.  It would be nice to have sn portion of kernel
Ken> code free of asm statement in the source. I heard that gcc is
Ken> also going in the direction of implementing intrinsic in the long
Ken> term.  Or do we have an option of CONFIG_NON_SGI?  I can cook up
Ken> something if this is really what people Want (I suspect not).

Ken,

Speaking solely on my own behalf, and not that of my employer here.

I have to say that I have always found it very discouraging how the
kernel had this mess added which is badly obfuscating the code solely
to support one vendor's broken compiler.

The real solution to this problem would be for Intel's compiler people
to fix the brokenness of ICC instead of adding any more of this
obfuscation to the kernel ;-(

Regards,
Jes

  parent reply	other threads:[~2006-01-31 10:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-27  1:37 [patch 5/5] fix sn rw_mmr.h to use intrinsic Chen, Kenneth W
2006-01-27  3:57 ` Chen, Kenneth W
2006-01-27  9:57 ` Jes Sorensen
2006-01-27 23:35 ` Chen, Kenneth W
2006-01-31 10:57 ` Jes Sorensen [this message]
2006-01-31 11:19 ` Christoph Hellwig
2006-01-31 18:08 ` Luck, Tony
2006-02-02  9:39 ` Jes Sorensen
2006-02-02 14:18 ` Jack Steiner
2006-02-02 18:54 ` Luck, Tony
2006-02-02 21:01 ` Jes Sorensen
2006-02-03 23:40 ` Gerald Pfeifer

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=yq04q3kr7ge.fsf@jaguar.mkp.net \
    --to=jes@trained-monkey.org \
    --cc=linux-ia64@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