Changes between Version 17 and Version 18 of AppPlanSpec

Timestamp:

Jun 27, 2014, 1:44:20 AM (10 years ago)

Author:

bema

Comment:

--

AppPlanSpec

@@ -32 +32 @@
    For example, if you have both SSE and non-SSE versions, use 1.1 and 1.0 respectively.
  <os_regex>regex</os_regex>:: use only hosts whose operating system version matches the given regular expression
+ <min_os_version>x</min_os_version>:: use only hosts which provide this minimal numerical OS version.
+   Numerical OS version is defined only for Microsoft Windows and Darwin (Apple Mac OSX) and parsed from the numerical
+   information provided by the client in the os_version string.
+   Examples:
+      1) plan class requires OSX "Lion" 10.7.0, client reports Darwin "11.00.00", min_os_version 110000.
+      2) plan class requires Windows 7 SP1, client reports "(Microsoft Windows 7 ..., Service Pack 1, (06.01.7601.00))", min_os_version is 601760100.
+ <max_os_version>x</max_os_version>:: max numerical OS version (see above)
  <cpu_feature>x</cpu_feature>:: a required CPU feature (such as sse3). You can include more than one.
  <host_summary_regex>regex</host_summary_regex>:: only sends the app version to hosts with host.serialnum field that matches the given regular expression.
@@ -38 +45 @@
  <project_prefs_tag>x</project_prefs_tag>:: the name of the tag
  <project_prefs_regex>x</project_prefs_regex>:: the contents must match this regular expression
+ <project_prefs_default_true/> treat the absence of the project_prefs_tag (i.e. the user didn't set it yet) as if the project_prefs_regex matched.
+
 
 Fields for multicore apps:
@@ -117 +126 @@
  <min_opencl_version>MMmm</min_opencl_version>:: minimum OpenCL version
  <max_opencl_version>MMmm</max_opencl_version>:: maximum OpenCL version
+ <double_precision_fp>:: reject plan class if the device doesn't support double precision floating point math
 
 Fields for OpenCL apps for AMD