- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 55 for we (0.19 sec)
-
src/cmd/asm/internal/asm/testdata/386.s
// This input was created by taking the instruction productions in // the old assembler's (8a's) grammar and hand-writing complete // instructions for each rule, to guarantee we cover the same space. #include "../../../../../runtime/textflag.h" TEXT foo(SB), DUPOK|NOSPLIT, $0 // LTYPE1 nonrem { outcode(int($1), &$2); } SETCC AX SETCC foo+4(SB) // LTYPE2 rimnon { outcode(int($1), &$2); } DIVB AX DIVB foo+4(SB) PUSHL $foo+4(SB)
Others - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Tue Apr 09 18:57:21 GMT 2019 - 2K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/tensorflow_issue_template.yaml
validations: required: true - type: markdown attributes: value: | Please make sure that this is a bug. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. - type: dropdown id: tf-nightly attributes: label: Have you reproduced the bug with TensorFlow Nightly?
Others - Registered: Tue May 07 12:40:20 GMT 2024 - Last Modified: Wed Jun 28 18:25:42 GMT 2023 - 3.7K bytes - Viewed (0) -
manifests/charts/default/templates/mutatingwebhook.yaml
# Adapted from istio-discovery/templates/mutatingwebhook.yaml # Removed paths for legacy and default selectors since a revision tag # is inherently created from a specific revision {{/* Copy just what we need to avoid expensive deepCopy */}} {{- $whv := dict "revision" .Values.revision "injectionURL" .Values.istiodRemote.injectionURL "namespace" .Release.Namespace }} {{- define "core" }} - name: {{.Prefix}}sidecar-injector.istio.io clientConfig:
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 3.7K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/feature_enhancement_request.yaml
it just seem like a sensible behavior for the feature to have? Before we make significant changes to existing features in Guava, we really want to be sure that it's for a use case that actually comes up in the real world. We want to hear the real-world use case so the community can discuss and debate whether this feature is actually
Others - Registered: Fri May 03 12:43:13 GMT 2024 - Last Modified: Fri Nov 17 18:47:47 GMT 2023 - 3.9K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/zzz_profile.yaml
Complex logic ahead... We have three sets of values, in order of precedence (last wins): 1. The builtin values.yaml defaults 2. The profile the user selects 3. Users input (-f or --set) Unfortunately, Helm provides us (1) and (3) together (as .Values), making it hard to insert (2). However, we can workaround this by placing all of (1) under a specific key (.Values.defaults).
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Tue Apr 02 22:30:06 GMT 2024 - 1.5K bytes - Viewed (0) -
manifests/charts/istio-control/istio-discovery/templates/configmap.yaml
{{- end }} {{- else }} discoveryAddress: istiod{{- if not (eq .Values.revision "") }}-{{ .Values.revision }}{{- end }}.{{.Release.Namespace}}.svc:15012 {{- end }} {{- end }} {{/* We take the mesh config above, defined with individual values.yaml, and merge with .Values.meshConfig */}} {{/* The intent here is that meshConfig.foo becomes the API, rather than re-inventing the API in values.yaml */}}
Others - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Thu Apr 18 18:16:49 GMT 2024 - 4.9K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/02-pkgsite-removal.yml
attributes: label: "What is the reason that you could not retract this package instead?" description: | Requesting we remove a module here only hides the generated documentation on pkg.go.dev. It does not affect the behaviour of proxy.golang.org or the go command. Instead we recommend using the retract directive which will be processed by all 3 of the above.
Others - Registered: Tue May 07 11:14:38 GMT 2024 - Last Modified: Thu Jan 04 23:31:17 GMT 2024 - 1.9K bytes - Viewed (0) -
src/cmd/asm/internal/asm/testdata/amd64dynlinkerror.s
// Copyright 2021 The Go Authors. All rights reserved. // Use of this source code is governed by a BSD-style // license that can be found in the LICENSE file. // Test to make sure that if we use R15 after it is clobbered by // a global variable access while dynamic linking, we get an error. // See issue 43661. TEXT ·a1(SB), 0, $0-0 CMPL runtime·writeBarrier(SB), $0 MOVL $0, R15 RET TEXT ·a2(SB), 0, $0-0 CMPL runtime·writeBarrier(SB), $0
Others - Registered: Tue Apr 30 11:13:12 GMT 2024 - Last Modified: Wed Mar 15 20:45:41 GMT 2023 - 4.8K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/bug-report.yaml
validations: required: true - type: textarea id: repro attributes: label: How can we reproduce it (as minimally and precisely as possible)? validations: required: true - type: textarea id: additional attributes: label: Anything else we need to know? - type: textarea id: kubeVersion attributes: label: Kubernetes version value: |
Others - Registered: Fri May 03 09:05:14 GMT 2024 - Last Modified: Mon Feb 28 09:34:43 GMT 2022 - 2.2K bytes - Viewed (0)