From: Andi Kleen <ak@muc.de>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Remove SSE2 bugs.h check
Date: Fri, 29 Aug 2003 19:42:36 +0200 [thread overview]
Message-ID: <20030829174236.GA11273@averell> (raw)
Remove some dead code.
CONFIG_SSE2 hasn't been defined for some time, because everything
SSE related is handled at runtime based on cpuid.
-Andi
diff -u linux-2.6.0test4-work/include/asm-i386/bugs.h-o linux-2.6.0test4-work/include/asm-i386/bugs.h
--- linux-2.6.0test4-work/include/asm-i386/bugs.h-o 2003-05-27 03:00:24.000000000 +0200
+++ linux-2.6.0test4-work/include/asm-i386/bugs.h 2003-08-29 19:39:15.000000000 +0200
@@ -193,11 +193,6 @@
&& (boot_cpu_data.x86_mask < 6 || boot_cpu_data.x86_mask == 11))
panic("Kernel compiled for PMMX+, assumes a local APIC without the read-before-write bug!");
#endif
-
-#ifdef CONFIG_X86_SSE2
- if (!cpu_has_sse2)
- panic("Kernel compiled for SSE2, CPU doesn't have it.");
-#endif
}
extern void alternative_instructions(void);
reply other threads:[~2003-08-29 17:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030829174236.GA11273@averell \
--to=ak@muc.de \
--cc=akpm@osdl.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;
as well as URLs for NNTP newsgroup(s).