| /aosp_15_r20/external/curl/tests/ |
| H A D | globalconfig.pm | 36 our @EXPORT = qw(
82 our $verbose; # 1 to show verbose test output
83 our $torture; # 1 to enable torture testing
84 our $proxy_address; # external HTTP proxy address
85 our $listonly; # only list the tests
86 our $run_event_based; # run curl with --test-event to test the event API
87 our $automakestyle; # use automake-like test status output format
88 our $anyway; # continue anyway, even if a test fail
89 our $CURLVERSION=""; # curl's reported version number
90 our $CURLVERNUM=""; # curl's reported version number (without -DEV)
[all …]
|
| H A D | sshhelp.pm | 33 our @EXPORT_OK = qw(
79 our $sshdexe = 'sshd' .exe_ext('SSH'); # base name and ext of ssh daemon
80 our $sshexe = 'ssh' .exe_ext('SSH'); # base name and ext of ssh client
81 our $sftpsrvexe = 'sftp-server' .exe_ext('SSH'); # base name and ext of sftp-server
82 our $sftpexe = 'sftp' .exe_ext('SSH'); # base name and ext of sftp client
83 our $sshkeygenexe = 'ssh-keygen' .exe_ext('SSH'); # base name and ext of ssh-keygen
84 our $httptlssrvexe = 'gnutls-serv' .exe_ext('SSH'); # base name and ext of gnutls-serv
85 our $sshdconfig = 'curl_sshd_config'; # ssh daemon config file
86 our $sshconfig = 'curl_ssh_config'; # ssh client config file
87 our $sftpconfig = 'curl_sftp_config'; # sftp client config file
[all …]
|
| /aosp_15_r20/external/llvm/docs/tutorial/ |
| H A D | BuildingAJIT1.rst | 35 - `Chapter #4 <BuildingAJIT4.html>`_: Improve the laziness of our JIT by
43 To provide input for our JIT we will use the Kaleidoscope REPL from
46 code for that chapter and replace it with optimization support in our JIT class
61 compiler does. To support that aim our initial, bare-bones JIT API will be:
92 In the previous section we described our API, now we examine a simple
96 input for our JIT: Each time the user enters an expression the REPL will add a
99 use the findSymbol method of our JIT class find and execute the code for the
102 of this tutorial we'll modify the REPL to enable new interactions with our JIT
103 class, but for now we will take this setup for granted and focus our attention on
104 the implementation of our JIT itself.
[all …]
|
| H A D | LangImpl09.rst | 28 our program down to something small and standalone. As part of this
73 First we make our anonymous function that contains our top level
74 statement be our "main":
147 our piece of Kaleidoscope language down to an executable program via this
162 construct one for our fib.ks file.
176 of our IR level descriptions. Construction for it takes a module so we
177 need to construct it shortly after we construct our module. We've left it
180 Next we're going to create a small container to cache some of our frequent
181 data. The first will be our compile unit, but we'll also write a bit of
182 code for our one type since we won't have to worry about multiple typed
[all …]
|
| /aosp_15_r20/external/sdv/vsomeip/third_party/boost/tti/doc/ |
| D | tti_nested_type.qbk | 20 The macro takes a single parameter, which is the name of a nested type. We will call this our
24 As with our other macros we can use the alternative form of the macro
27 of our resulting metafunction is exactly the same.
88 to use it in our template instantiation of one of TTI's macro metafunctions.
92 types we have and that a nested type exists, and these declarations are within our scope, we can
114 from our metafunction, which is the same type as a nested type if it exists or some other
116 compiler error. If we had to use the 'T::InnerType' syntax to specify our type, where 'T' represents
117 out enclosing type and 'InnerType' our nested type, and there was no nested type 'InnerType' within…
124 when doing metafunction programming. Occasionally the TTI produced marker type, when our nested
136 we will want to ask if the type is really our nested type or the marker type instead. Essentially
[all …]
|
| /aosp_15_r20/cts/hostsidetests/gputools/src/android/gputools/cts/ |
| H A D | CtsRootlessGpuDebugHostTest.java | 244 // Give our activity a chance to run and fill the log in scanLog()
317 * Launch our test as a background service, avoiding any platform rendering code
331 …* This is the primary test of the feature. It pushes layers to our debuggable app and ensures they…
343 // Copy the layers from our LAYERS APK to tmp in testDebugLayerLoadVulkan()
347 // Copy them over to our DEBUG app in testDebugLayerLoadVulkan()
355 // Kick off our DEBUG app in testDebugLayerLoadVulkan()
378 // Copy a layer from our LAYERS APK to tmp in testLayerNotLoadedVulkan()
381 // Attempt to copy them over to our RELEASE or INJECT app (this should fail) in testLayerNotLoadedVulkan()
386 // Kick off our app in testLayerNotLoadedVulkan()
427 // Copy a layer from our LAYERS APK to tmp in testDebugNotEnabledVulkan()
[all …]
|
| /aosp_15_r20/development/samples/ApiDemos/src/com/example/android/apis/view/ |
| H A D | List6.java | 43 // Use our own list adapter in onCreate()
68 * in our array.
121 * Remember our context so we can use it when constructing views.
126 * Our data, part 1.
141 * Our data, part 2.
171 "For our advantage on the bitter cross." +
172 "But this our purpose now is twelve month old," +
176 "What yesternight our council did decree" +
219 "To rank our chosen truth with such a show" +
221 "Our own brains, and the opinion that we bring," +
[all …]
|
| /aosp_15_r20/external/rust/android-crates-io/crates/csv/src/ |
| D | tutorial.rs | 85 Let's make our program do something useful. Our program will read CSV data on
117 Assuming that succeeds, let's try running our program. But first, we will need
142 our previous example to show errors in a more friendly way. **If you're already
186 With our new found knowledge, let's re-examine our previous example and dissect
237 So what actually causes the panic to happen in our program? That would be the
238 first line in our loop:
279 We'll convert our unrecoverable error to a recoverable error in 3 steps. First,
289 // Examine our Result.
303 If we run our program again, we'll still see an error message, but it is no
316 The second step for moving to recoverable errors is to put our CSV record loop
[all …]
|
| /aosp_15_r20/development/samples/ApiDemos/src/com/example/android/apis/ |
| H A D | Shakespeare.java | 5 * Our data, part 1.
20 * Our data, part 2.
50 "For our advantage on the bitter cross." +
51 "But this our purpose now is twelve month old," +
55 "What yesternight our council did decree" +
98 "To rank our chosen truth with such a show" +
100 "Our own brains, and the opinion that we bring," +
106 "The very persons of our noble story" +
132 "Now is the winter of our discontent" +
134 "And all the clouds that lour'd upon our house" +
[all …]
|
| /aosp_15_r20/external/pigweed/docs/ |
| H A D | mission.rst | 8 Our Mission
15 Each component of our mission has additional meaning:
17 - **Software** - Our modular components and surrounding tooling are our
18 primary deliverable. The software is the product of our philosophies.
20 all teams have time for. Our mission is to create reusable processes that can
21 save time and increase team happiness. Our approach is to offer tooling and
22 standards. For example, our integrated code formatting, module directory
25 related products; and over time the requirements change. Our mission is to
26 make these sustained development situations easier. Our approach is to create
28 our porting abstractions make switching a microcontroller vendor easier.
[all …]
|
| /aosp_15_r20/external/apache-commons-lang/src/test/java/org/apache/commons/lang3/function/ |
| H A D | FailableFunctionsTest.java | 1389 …* Tests that our failable interface is properly defined to throw any exception using the top level…
1404 …* Tests that our failable interface is properly defined to throw any exception using String and IO…
1420 …* Tests that our failable interface is properly defined to throw any exception using the top level…
1435 …* Tests that our failable interface is properly defined to throw any exception using String and IO…
1450 …* Tests that our failable interface is properly defined to throw any exception using the top level…
1465 …* Tests that our failable interface is properly defined to throw any exception using String and IO…
1480 …* Tests that our failable interface is properly defined to throw any exception using String and IO…
1495 …* Tests that our failable interface is properly defined to throw any exception using the top level…
1510 …* Tests that our failable interface is properly defined to throw any exception using the top level…
1525 …* Tests that our failable interface is properly defined to throw any exception using String and IO…
[all …]
|
| /aosp_15_r20/external/cronet/third_party/rust/chromium_crates_io/vendor/aho-corasick-1.1.3/src/packed/teddy/ |
| H A D | README.md | 87 matches, then a verification step is performed. In this implementation, our
91 pick our fingerprints. In Hyperscan's implementation, I *believe* they use the
98 some examples to motivate the approach. Here are our patterns:
107 our 16 byte block to:
117 this case, our fingerprint is a single byte, so an appropriate abstraction is
127 we can make is to represent our patterns as bit fields occupying a single
143 If we could somehow cause `B` to contain our 16 byte block from the haystack,
144 and if `A` could contain our bitmasks, then we'd end up with something like
152 And if `B` contains our window from our haystack, we could use shuffle to take
153 the values from `B` and use them to look up our bitsets in `A`. But of course,
[all …]
|
| /aosp_15_r20/external/rust/android-crates-io/crates/aho-corasick/src/packed/teddy/ |
| D | README.md | 87 matches, then a verification step is performed. In this implementation, our
91 pick our fingerprints. In Hyperscan's implementation, I *believe* they use the
98 some examples to motivate the approach. Here are our patterns:
107 our 16 byte block to:
117 this case, our fingerprint is a single byte, so an appropriate abstraction is
127 we can make is to represent our patterns as bit fields occupying a single
143 If we could somehow cause `B` to contain our 16 byte block from the haystack,
144 and if `A` could contain our bitmasks, then we'd end up with something like
152 And if `B` contains our window from our haystack, we could use shuffle to take
153 the values from `B` and use them to look up our bitsets in `A`. But of course,
[all …]
|
| /aosp_15_r20/frameworks/base/tests/VoiceInteraction/res/values/ |
| H A D | strings.xml | 88 For our advantage on the bitter cross.\n
89 But this our purpose now is twelve month old,\n
93 What yesternight our council did decree\n
136 To rank our chosen truth with such a show\n
138 Our own brains, and the opinion that we bring,\n
144 The very persons of our noble story\n
170 Now is the winter of our discontent\n
172 And all the clouds that lour\'d upon our house\n
174 Now are our brows bound with victorious wreaths;\n
175 Our bruised arms hung up for monuments;\n
[all …]
|
| /aosp_15_r20/external/sdv/vsomeip/third_party/boost/fusion/doc/ |
| D | extension.qbk | 23 [heading Our example]
58 Next we need to enable the `traits::tag_of` metafunction to return our newly chosen
59 tag type for operations involving our sequence. This is done by specializing
60 `traits::tag_of` for our sequence type.
76 for our sequence, but for an example see the code in:
84 the data within our sequence. As it is straightforward to do,
85 we are going to provide a random access iterator in our example.
106 A quick summary of the details of our iterator:
115 We also need to enable __tag_dispatching__ for our iterator type, with another specialization of
119 add features to our implementation.
[all …]
|
| /aosp_15_r20/tools/security/fuzzing/orphans/libffi/ |
| H A D | fuzz_ffi.cc | 25 // Empty functions we can use for our function targets
35 // Set our flag so we don't call a java-related function (triggers an abort) in generateCustomType()
45 // Generate our subobjects in generateCustomType()
62 // Get our size/alignment in generateCustomType()
89 // Which type? Let type==NUM_TYPES be our custom struct case in getRandomType()
107 // Allocate the space for our arg in genArg()
127 // The first value in our array should be the number of arguments in buildArgArrays()
133 // Grab our arguments in buildArgArrays()
142 // Generate a value for it and add to our arguments array in buildArgArrays()
146 // Our arrays of pointers need to be nullptr-terminated in buildArgArrays()
[all …]
|
| /aosp_15_r20/external/crosvm/hypervisor/src/kvm/ |
| H A D | x86_64.rs | 243 … // Safe because we know that our file is a VM fd, we know the kernel will only write correct in get_pvclock_arch()
244 // amount of memory to our pointer, and we verify the return result. in get_pvclock_arch()
257 // Safe because we know that our file is a VM fd, we know the kernel will only read correct in set_pvclock_arch()
258 // amount of memory from our pointer, and we verify the return result. in set_pvclock_arch()
277 // Safe because we know our file is a VM fd, we know the kernel will only write in get_pic_state()
278 // correct amount of memory to our pointer, and we verify the return result. in get_pic_state()
303 // Safe because we know that our file is a VM fd, we know the kernel will only read in set_pic_state()
304 // correct amount of memory from our pointer, and we verify the return result. in set_pic_state()
328 // Safe because we know our file is a VM fd, we know the kernel will only write in get_ioapic_state()
329 // correct amount of memory to our pointer, and we verify the return result. in get_ioapic_state()
[all …]
|
| /aosp_15_r20/build/bazel/scripts/ |
| H A D | apex_compare.sh | 7 # Soong), the second is "our" APEX (built by Bazel).
11 # - missing files (those in the reference APEX missing from our APEX)
12 # - extra files (those only in our APEX)
123 mount_and_list ext2 $our_img $fuse_dir/our.img >$fuse_dir/our.img.list
124 . <(classify $fuse_dir/ref.img.list $fuse_dir/our.img.list; /bin/true)
132 cmp -s $fuse_dir/{ref,our}.img/$f && continue
136 diff $fuse_dir/{ref,our}.img/$f || /bin/true
139 …<(dump_apex_manifest <$fuse_dir/ref.img/$f) <(dump_apex_manifest <$fuse_dir/our.img/$f) || bin/true
143 sizes=($(stat --format "%s" $fuse_dir/{ref,our}.img/$f))
168 mkdir -p $fuse_dir/{our,ref}.{apex,img}
[all …]
|
| /aosp_15_r20/external/python/watchdog/ |
| D | changelog.rst | 13 - Thanks to our beloved contributors: @gnought, @BoboTiG
21 - Thanks to our beloved contributors: @apoirier, @BoboTiG
47 - Thanks to our beloved contributors: @BoboTiG
62 - Thanks to our beloved contributors: @BoboTiG, @nbelakovski, @ivg
70 - Thanks to our beloved contributors: @mraspaud, @BoboTiG
87 - Thanks to our beloved contributors: @BoboTiG, @msabramo
102 - Thanks to our beloved contributors: @kurtmckee, @altendky, @agroszer, @BoboTiG
113 - Thanks to our beloved contributors: @BoboTiG
124 - Thanks to our beloved contributors: @BoboTiG, @dstaple, @taleinat, @cernekj
135 - Thanks to our beloved contributors: @BoboTiG, @simon04, @piotrpdev
[all …]
|
| /aosp_15_r20/external/apache-xml/test/java/src/org/apache/qetest/xsl/ |
| H A D | ThreadedStylesheetTestlet.java | 59 // Initialize our classname for TestletImpl's main() method
62 // Initialize our defaultDatalet
65 /** Accessor for our Datalet instead of calling execute(). */
74 /* Description of our current state; changes during our lifecycle. */
81 * description of our current result or status.
93 * Automatically adds our identifier at the start.
95 * @param d String to set as our current description.
102 /* Our 'final' test result; actually changes during our lifecycle. */
149 // All the rest of the test is executed in our thread. in execute()
153 …gger.CRITICALMSG, "//@todo execute() is not yet implemented - you must start our thread yourself"); in execute()
[all …]
|
| /aosp_15_r20/external/brotli/tests/testdata/ |
| H A D | plrabn12.txt | 19 something we could massage with our favorite 486 in DOS. After
29 In the course of our searches for Professor Raben and his etext
36 totally unrelated action to our searches for him, the professor
57 Gutenberg. The first was released as our October, 1991 etext.
73 Brought death into the World, and all our woe,
99 Moved our grand parents, in that happy state,
192 Irreconcilable to our grand Foe,
211 Though all our glory extinct, and happy state
213 But what if he our Conqueror (whom I now
216 Have left us this our spirit and strength entire,
[all …]
|
| /aosp_15_r20/external/sdv/vsomeip/third_party/boost/spirit/doc/x3/tutorial/ |
| D | annotation.qbk | 18 trees) in our previoius examples. We parsed a single structure and generated
39 First, we'll update our previous employee struct, this time separating the
68 Like before, we need to tell __fusion__ about our structs to make them
110 imperative code. But semantic actions mess up our clean declarative grammars.
111 If we care to keep our code clean, `on_success` handlers are alternative
121 our `on_success` handler:
141 Our `on_success` handler gets a reference to the actual `position_cache` and
148 Now we'll write a parser for our employee. To simplify, inputs will be of the
216 By subclassing the rule class from a client supplied handler such as our
233 For our particular example, we use to inject the `position_cache` into the
[all …]
|
| /aosp_15_r20/build/bazel/mkcompare/ |
| H A D | mkdiff.go | 35 var normalizer = map[string]func(ref, our string) (string, string){
43 func normalizePrebuiltModuleFile(ref string, our string) (string, string) {
44 …return strings.ReplaceAll(ref, "/bazelCombined/", "/combined/"), strings.ReplaceAll(our, "/bazelCo…
49 func normalizeInstallPairs(ref string, our string) (string, string) {
50 … rexRemoveInstallSource.ReplaceAllString(ref, ""), rexRemoveInstallSource.ReplaceAllString(our, "")
59 // MkModuleDiff holds module difference between reference and our mkfile.
62 Our *MkModule `json:"-"` member
80 fmt.Fprintf(sink, "%s (ref line %d, our line %d):\n", name, d.Ref.Location, d.Our.Location)
82 fmt.Fprintf(sink, " type %s <-> %s\n", d.Ref.Type, d.Our.Type)
86 fmt.Fprintf(sink, " extras %d <-> %d\n", d.Ref.Extras, d.Our.Extras)
[all …]
|
| /aosp_15_r20/external/flatbuffers/swift/Sources/FlatBuffers/Documentation.docc/Tutorials/ |
| H A D | create_your_first_buffer.tutorial | 2 @Intro(title: "After having our code generated") {
3 …After generating the code from the previous section, we will know start creating our monster objec…
11 Starting with a new file, we will create our very first Flatbuffer.
24 … After creating the builder, we can start serializing our data. Before we make our orc Monster,
25 …let's create some Weapons: a Sword and an Axe. However we will start by naming our weapons as `Swo…
35 …We will take our (Sword and Axe) serialized data and serialize their offsets as a vector of tables…
36 So we can reference them later on from our Monster Object
40 We will add our Monster name as a string value just like we did with the weapons.
45 …We will create a path that our monster should be using while roaming in its den. To create a vecto…
55 …Now to serialize our data into our `Monster` object. Which again there are two ways of doing, by c…
[all …]
|
| /aosp_15_r20/external/crosvm/kvm/src/ |
| H A D | lib.rs | 168 // Safe because we know that our file is a KVM fd and that the extension is one of the ones in check_extension_int()
181 // Safe because we know that our file is a KVM fd and we verify the return result. in get_vcpu_mmap_size()
391 // Safe because we know that our file is a KVM fd and that the extension is one of the ones in check_extension()
521 // Safe because we know that our file is a VM fd and we verify the return result. in set_identity_map_addr()
538 // Safe because we know that our file is a VM fd, we know the kernel will only write in get_clock()
539 // correct amount of memory to our pointer, and we verify the return result. in get_clock()
554 // Safe because we know that our file is a VM fd, we know the kernel will only read in set_clock()
555 // correct amount of memory from our pointer, and we verify the return result. in set_clock()
570 // Safe because we know that our file is a VM fd and we verify the return result. in create_irq_chip()
589 // Safe because we know our file is a VM fd, we know the kernel will only write in get_pic_state()
[all …]
|