Searched refs:workaround (Results 1 – 25 of 444) sorted by relevance
12345678910>>...18
/external/arm-trusted-firmware/docs/design/ |
D | cpu-specific-build-macros.rst | 14 - ``WORKAROUND_CVE_2017_5715``: Enables the security workaround for 16 of the PEs in the system need the workaround. Setting this flag to 0 provides 18 with the recommendation in the spec regarding workaround discovery. 21 - ``WORKAROUND_CVE_2018_3639``: Enables the security workaround for 25 regarding workaround discovery. 47 errata workaround is identified by its ``ID`` as specified in the processor's 49 errata workaround is ``ERRATA_<Processor name>_<ID>``, where the ``Processor name`` 53 write errata workaround functions. 57 errata workaround build flags in the platform specific makefile. In case 59 workaround is not applied. In the DEBUG build, this is indicated by [all …]
|
/external/brotli/java/org/brotli/wrapper/enc/ |
D | BUILD | 46 ":brotli_jni", # Bazel JNI workaround 62 ":brotli_jni", # Bazel JNI workaround 78 ":brotli_jni", # Bazel JNI workaround
|
/external/brotli/java/org/brotli/wrapper/dec/ |
D | BUILD | 45 ":brotli_jni", # Bazel JNI workaround 60 ":brotli_jni", # Bazel JNI workaround 75 ":brotli_jni", # Bazel JNI workaround
|
/external/rust/crates/grpcio-sys/grpc/ |
D | WORKSPACE | 31 # pools through labels, we use a workaround and populate the corresponding label values 33 # Remove this workaround once we transition to a new-enough bazel toolchain. 57 # pools through labels, we use a workaround and populate the corresponding label values 59 # Remove this workaround once we transition to a new-enough bazel toolchain.
|
/external/tensorflow/third_party/toolchains/java/ |
D | BUILD | 1 # For workaround https://github.com/bazelbuild/bazel/issues/8772 with Bazel >= 0.29.1 5 # the compiling action will fail. To workaround this, we override the misc value of
|
/external/tflite-support/third_party/toolchains/java/ |
D | BUILD | 1 # For workaround https://github.com/bazelbuild/bazel/issues/8772 with Bazel >= 0.29.1 5 # the compiling action will fail. To workaround this, we override the misc value of
|
/external/brotli/java/org/brotli/wrapper/common/ |
D | BUILD | 41 ":brotli_jni_no_dictionary_data", # Bazel JNI workaround 54 ":brotli_jni_no_dictionary_data", # Bazel JNI workaround
|
/external/mesa3d/docs/relnotes/ |
D | 13.0.3.rst | 106 - radeonsi: apply a multi-wave workgroup SPI bug workaround to affected 108 - radeonsi: apply a TC L1 write corruption workaround for SI 109 - radeonsi: apply a tessellation bug workaround for SI 110 - radeonsi: add a tess+GS hang workaround for VI dGPUs 111 - radeonsi: apply the double EVENT_WRITE_EOP workaround to VI as well
|
D | 17.2.2.rst | 63 - radv: add gfx9 scissor workaround 104 - cherry-ignore: add "radeonsi/gfx9: proper workaround for LS/HS VGPR 136 - radeonsi: workaround for gather4 on integer cube maps 138 - amd/common: add workaround for cube map array layer clamping
|
D | 18.0.3.rst | 68 - radeonsi/gfx9: workaround for INTERP with indirect indexing 72 - i965/tex_image: Avoid the ASTC LDR workaround on gen9lp
|
D | 17.1.10.rst | 49 instancing bug workaround on SI" 95 - cherry-ignore: add "amd/common: add workaround for cube map array 97 - cherry-ignore: add "radeonsi: workaround for gather4 on integer cube
|
/external/skqp/tools/ |
D | build_workaround_header.py | 26 workarounds.update([workaround.strip() for workaround in f])
|
/external/skia/tools/ |
D | build_workaround_header.py | 26 workarounds.update([workaround.strip() for workaround in f])
|
/external/arm-trusted-firmware/docs/security_advisories/ |
D | security-advisory-tfv-6.rst | 53 Secure-EL1 and executing the ``BPIALL`` instruction. This workaround is 54 significantly more complex than the "MMU disable/enable" workaround. The latter 61 work. If that other privileged software is able to workaround the vulnerability 66 implementing a specified `CVE-2017-5715`_ workaround SMC 81 with MMU disabled that this workaround entails effectively does invalidate the 118 workaround should be provided by vendors of that software and is outside the
|
/external/llvm/test/CodeGen/X86/ |
D | init-priority.ll | 8 ; This is to workaround a Visual Studio bug which causes field 11 ; This workaround consists in providing a user default constructor
|
/external/llvm-project/llvm/test/CodeGen/X86/ |
D | init-priority.ll | 8 ; This is to workaround a Visual Studio bug which causes field 11 ; This workaround consists in providing a user default constructor
|
/external/rust/crates/grpcio-sys/grpc/third_party/toolchains/ |
D | BUILD | 42 # pools through labels, we use a workaround and populate the corresponding label values 44 # Remove this workaround once we transition to a new-enough bazel toolchain.
|
/external/eigen/doc/ |
D | UsingNVCC.dox | 18 …or greater) has issues with the standard \c \<limits\> header file. To workaround this, you can ad… 20 // workaround issue between gcc >= 4.7 and cuda 5.5
|
/external/eigen/cmake/ |
D | language_support.cmake | 6 # This additional function definition is needed to provide a workaround for 19 # My workaround is to invoke cmake twice. If both return codes are zero,
|
/external/kotlinx.coroutines/stdlib-stubs/ |
D | README.md | 1 This is a workaround for Dokka to generate proper references for Kotlin 1.3 API.
|
/external/kotlinx.coroutines/js/js-stub/ |
D | README.md | 1 This is a workaround for Dokka to generate proper references for JS modules.
|
/external/tensorflow/tensorflow/security/advisory/ |
D | tfsa-2020-003.md | 36 A potential workaround would be to add a custom `Verifier` to limit the maximum 42 inference steps, then there are no possible workaround and users are advised to
|
D | tfsa-2020-004.md | 39 A potential workaround would be to add a custom `Verifier` to the model loading 47 then there are no possible workaround and users are advised to upgrade to
|
/external/rust/crates/vmm_vhost/.cargo/ |
D | config | 1 # This workaround is needed because the linker is unable to find __addtf3,
|
/external/grpc-grpc/doc/ |
D | fork_support.md | 28 We have provided a workaround for this issue by allowing users to turn 42 The workaround when using fork/exec by setting
|
12345678910>>...18