OpenGrok
Home
Sort by relevance
Sort by last modified time
Full Search
Definition
Symbol
File Path
History
|
|
Help
Searched
full:textual
(Results
526 - 550
of
1476
) sorted by null
<<
21
22
23
24
25
26
27
28
29
30
>>
/external/clang/docs/
Modules.rst
35
* **Fragility**: ``#include`` directives are treated as
textual
74
Modules improve access to the API of software libraries by replacing the
textual
preprocessor inclusion model with a more robust, more efficient semantic model. From the user's perspective, the code looks only slightly different, because one uses an ``import`` declaration rather than a ``#include`` preprocessor directive:
277
textual
header "assert.h"
316
``exclude`` ``header`` ``
textual
``
454
``private``:sub:`opt` ``
textual
``:sub:`opt` ``header`` *string-literal*
458
A header declaration that does not contain ``exclude`` nor ``
textual
`` specifies a header that contributes to the enclosing module. Specifically, when the module is built, the named header will be parsed and its declarations will be (logically) placed into the enclosing submodule.
470
A header with the ``
textual
`` specifier will not be compiled when the module is
479
**Example:** The C header ``assert.h`` is an excellent candidate for a
textual
header, because it is meant to be included multiple times (possibly with different ``NDEBUG`` settings). However, declarations within it should typically be split into a separate modular header.
484
textual
header "assert.h"
[
all
...]
/external/clang/lib/Lex/
ModuleMap.cpp
319
// Prefer a non-
textual
header over a
textual
header.
[
all
...]
/external/avb/libavb/
avb_slot_verify.h
42
* Use avb_slot_verify_result_to_string() to get a
textual
108
/* Get a
textual
representation of |result|. */
/external/boringssl/src/
LICENSE
104
* This can be in the form of a
textual
message at program startup or
105
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/asn1/
a_int.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/base64/
base64.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/bio/
bio.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
connect.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/bn_extra/
convert.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/dh/
dh.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/dsa/
dsa_test.cc
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/fipsmodule/
FIPS.md
66
First, all the C source files for the module are compiled as a single unit by compiling a single source file that `#include`s them all (this is `bcm.c`). The `-fPIC` flag is used to cause the compiler to use IP-relative addressing in many (but not all) cases. Also the `-S` flag is used to instruct the compiler to produce a
textual
assembly file rather than a binary object file.
68
The
textual
assembly file is then processed by a script to merge in assembly implementations of some primitives and to eliminate the remaining sources of relocations.
/external/boringssl/src/crypto/fipsmodule/cipher/
cipher.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/fipsmodule/sha/
sha1-altivec.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
sha256.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/obj/
obj.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/crypto/x509/
a_strex.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
by_dir.c
20
* This can be in the form of a
textual
message at program startup or
21
* in documentation (online or
textual
) provided with the package.
x509_cmp.c
20
* This can be in the form of a
textual
message at program startup or
21
* in documentation (online or
textual
) provided with the package.
x_crl.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
x_name.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/decrepit/bio/
base64_bio.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/decrepit/ripemd/
internal.h
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
ripemd.c
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
/external/boringssl/src/include/openssl/
pem.h
19
* This can be in the form of a
textual
message at program startup or
20
* in documentation (online or
textual
) provided with the package.
Completed in 444 milliseconds
<<
21
22
23
24
25
26
27
28
29
30
>>