Searched refs:rules (Results 1 – 25 of 69) sorted by relevance
123
| /device/linaro/bootloader/edk2/AppPkg/Applications/Python/Python-2.7.2/Parser/ |
| D | spark.py | 105 self.rules = {}
155 self.rules = {}
174 rules = string.split(doc)
177 for i in range(len(rules)):
178 if rules[i] == '::=':
180 index.append(len(rules))
183 lhs = rules[index[i]]
184 rhs = rules[index[i]+2:index[i+1]]
190 if self.rules.has_key(lhs):
191 self.rules[lhs].append(rule)
[all …]
|
| /device/linaro/bootloader/edk2/EmbeddedPkg/ |
| D | EmbeddedPkg.fdf | 46 # The component or module type is used to reference the standard rules
59 # rules for the different module type. User can add the customized rules to define the
|
| /device/sample/apps/SetupCustomizer/ |
| D | proguard-project.txt | 4 # Add project specific ProGuard rules here.
|
| /device/sample/apps/LeanbackCustomizer/ |
| D | proguard-project.txt | 4 # Add project specific ProGuard rules here.
|
| /device/sample/apps/LeanbackWidget/ |
| D | proguard-project.txt | 4 # Add project specific ProGuard rules here.
|
| /device/linaro/bootloader/edk2/StdLib/LibC/Time/ |
| D | Theory.txt | 32 daylight saving time rules, or situations where more than two
50 the system supplies its own rules for DST, and these can
51 differ from year to year; typically US DST rules are used.
67 typically the current US DST rules are used,
68 but this means that the US DST rules are compiled into each program
70 rules change (as in the United States in 1987), all programs that
90 daylight time zone name. The daylight saving time rules to be used
92 the format of the file allows U.S., Australian, and other rules to be
219 Here are the general rules used for choosing location names,
260 violate the above rules. For example, don't change
[all …]
|
| /device/google/vrservices/vrcore/sepolicy/ |
| D | vrcore_app.te | 4 ### opportunistically eliminate legacy untrusted_app rules.
|
| /device/linaro/bootloader/edk2/UefiCpuPkg/ResetVector/Vtf0/ |
| D | ReadMe.txt | 8 In your FDF FFS file rules sections add:
|
| /device/sample/frameworks/PlatformLibrary/ |
| D | README.txt | 31 The top-level Android.mk defines the rules to build the shared library itself,
57 the rules for building the final .so in which the code lives. This example
|
| /device/linaro/bootloader/edk2/BaseTools/Source/C/VfrCompile/Pccts/antlr/ |
| D | antlr1.txt | 30 which eliminates the need for precedence rules.
35 parsers, arbitrary values may be inherited from parent rules
57 -cr Generate a cross-reference for all rules. For each
58 rule, print a list of all other rules that reference
255 for functions generated for rules.
|
| /device/linaro/bootloader/OpenPlatformPkg/Platforms/Hisilicon/HiKey/ |
| D | HiKey.fdf | 240 # rules for the different module type. User can add the customized rules to define the
265 # These SEC rules are used for ArmPlatformPkg/PrePi module.
|
| /device/linaro/bootloader/OpenPlatformPkg/Platforms/ARM/Juno/ |
| D | ArmJuno.fdf | 245 # rules for the different module type. User can add the customized rules to define the
270 # These SEC rules are used for ArmPlatformPkg/PrePi module.
|
| /device/linaro/bootloader/edk2/ArmPlatformPkg/ArmJunoPkg/ |
| D | ArmJuno.fdf | 245 # rules for the different module type. User can add the customized rules to define the
270 # These SEC rules are used for ArmPlatformPkg/PrePi module.
|
| /device/linaro/bootloader/edk2/CorebootPayloadPkg/ |
| D | CorebootPayloadPkg.fdf | 185 # rules for the different module type. User can add the customized rules to define the
|
| /device/linaro/bootloader/edk2/ArmPlatformPkg/ |
| D | ArmPlatformPkg-2ndstage.fdf | 166 # rules for the different module type. User can add the customized rules to define the
|
| D | ArmPlatformPkg.fdf | 223 # rules for the different module type. User can add the customized rules to define the
|
| /device/linaro/bootloader/OpenPlatformPkg/Platforms/TexasInstruments/BeagleBoard/ |
| D | BeagleBoardPkg.fdf | 212 # rules for the different module type. User can add the customized rules to define the
|
| /device/linaro/bootloader/edk2/BaseTools/Conf/ |
| D | target.template | 68 # BUILD_RULE_CONF Filename Optional Specify the file name to use for the build rules that are fol…
|
| /device/linaro/bootloader/edk2/BeagleBoardPkg/ |
| D | BeagleBoardPkg.fdf | 222 # rules for the different module type. User can add the customized rules to define the
|
| /device/linaro/bootloader/edk2/ArmPlatformPkg/ArmVExpressPkg/ |
| D | ArmVExpress-CTA15-A7.fdf | 226 # rules for the different module type. User can add the customized rules to define the
|
| D | ArmVExpress-RTSM-A15_MPCore.fdf | 268 # rules for the different module type. User can add the customized rules to define the
|
| /device/linaro/bootloader/edk2/Nt32Pkg/ |
| D | Nt32Pkg.fdf | 150 # The component or module type is used to reference the standard rules
289 # rules for the different module type. User can add the customized rules to define the
|
| /device/linaro/bootloader/OpenPlatformPkg/Platforms/ARM/VExpress/ |
| D | ArmVExpress-RTSM-A15_MPCore.fdf | 257 # rules for the different module type. User can add the customized rules to define the
|
| /device/linaro/bootloader/edk2/ArmVirtPkg/ |
| D | ArmVirtXen.fdf | 216 # rules for the different module type. User can add the customized rules to define the
|
| /device/linaro/bootloader/edk2/EdkCompatibilityPkg/Other/Maintained/Tools/Pccts/ |
| D | CHANGES_FROM_133_before_mr13.txt | 93 d. Apply these rules recursively.
145 other rule then all such rules are listed. This is useful for
146 alerting one to rules which are not used, but which can still
372 expressions or in the rules of the grammar.
1082 | One can implement these rules quite neatly using && predicates: |
1153 explores the rules which are reachable from
1290 The hoisting of predicates into rules to create prediction
1352 Chain of referenced rules:
2103 In rule "all" the alternatives which refer to rules "e" and "f" allow
2225 This is especially important for predicates formed by rules
[all …]
|
123