Changes between Version 22 and Version 23 of BoincPlatforms

Timestamp:

Sep 17, 2009, 4:48:42 PM (15 years ago)

Author:

davea

Comment:

--

BoincPlatforms

@@ -15 +15 @@
 
 BOINC defines a set of platforms (see below).
-If you want your application to exploit specific architectural features at a finer granularity,
-your application must recognize the features and branch to appropriate code.
-In other words, if you want to make a version of your application that can use the AMD 3DNow instruction set,
-don't create a new '''windows_amd_3dnow''' platform.
-Instead, make a version for the '''windows_intelx86''' platform that recognizes when it's running on a 3DNow machine,
-and branches to the appropriate code.
-
 Platforms are maintained in the '''platform''' table in the BOINC database.
 This is pre-populated with the 10 or so most common platforms.
@@ -29 +22 @@
 For coherence between projects, use only the following platforms.
 If you want to add a different platform, please [ProjectPeople contact us].
+
+You may have executables that exploit specific architectural features at a finer granularity
+than that of platform.
+For example, you may have an executable that uses AMD 3DNow instructions.
+There are two ways to arrange this:
+
+ * Use the [AppPlan application planning] mechanism to specify a class of app versions that can be sent only to hosts with particular CPU features;
+ * Make a "fat executable" that recognizes when it's running on a 3DNow machine,
+and branches to the appropriate code.
 
 ||  '''__Name__'''              ||  '''__Description__''' ||