From: Christoph Hellwig <hch@infradead.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 11:19:35 +0000 [thread overview]
Message-ID: <20060131111935.GA6699@infradead.org> (raw)
In-Reply-To: <200601270137.k0R1big21236@unix-os.sc.intel.com>
On Tue, Jan 31, 2006 at 05:57:05AM -0500, Jes Sorensen wrote:
> 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 ;-(
Agreed. Obsfucating for a propritary and pretty much irrelevant (for the
kernel) compiler is a horrible thing to do. And the only reason we do that
at all is that the compiler is from the same company that's behind ia64.
Please fix up your damn compiler. Even SGI managed to add proper inline
asflembly support to Pro64, and they had much less ressources.
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-01-31 11:19 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
2006-01-31 11:19 ` Christoph Hellwig [this message]
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=20060131111935.GA6699@infradead.org \
--to=hch@infradead.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