| /dports/lang/polyml/polyml-5.8.2/mlsource/MLCompiler/CodeTree/ |
| H A D | CODETREE_CODEGEN_CONSTANT_FUNCTIONS.sml | 87 EnvGenLoad load => SOME(Extract load)
124 | code => Declar{value=code, addr=addr, use=use} :: processBindings tail
184 Container{addr=addr, use=use, size=size,
214 NONE => EnvGenLoad load
220 EnvGenLoad load => EnvGenLoad(addToClosure newClosure load)
224 | lookupLocal load = EnvGenLoad load (* Argument *)
249 fun lookupAddr(load as LoadLocal n) =
252 NONE => EnvGenLoad load
281 (* The code may consist of tuples (i.e. compiled ML structures) containing
282 a mixture of Loads, where the values are yet to be compiled, and
[all …]
|
| /dports/devel/p5-Module-Compile/Module-Compile-0.23/ |
| H A D | README | 18 use Foo;
27 use Foo;
39 Modules that use these compilation modules get compiled into some
57 and use it like:
60 use v6-pugs;
70 The next time around, Perl 5 will automatically load MyModule.pmc when
89 * Easier debugging of compiled/filtered code. The ".pmc" has the real
93 has already been doing the ".pmc" check on every module load since
151 So inner blocks get compiled first, then outer blocks.
169 with compiled .pmc files. Module::Compile installs a
[all …]
|
| /dports/x11-fonts/psftools/psftools-1.0.13/dos16ppd/ |
| H A D | README | 4 This archive contains the PSF Tools as compiled for 16-bit DOS using
10 2. In the Unix version, the codepage tables are compiled into the programs.
13 be kept in the same directory as the programs if you want to use any
42 way -- convert to a CPI file and load that with DISPLAY.SYS and MODE.
52 DISPLAY.SYS and MODE do not. When asked to load a 512-character font, it
53 will select the first 256 characters for normal use and the second 256
58 --second: As above but use characters 256-511, not 0-255.
59 --alt: If loading a 256-character font, load it into the high intensity
64 On a Hercules system, attempts to load a PSF file larger than 256
|
| /dports/math/maxima/maxima-5.43.2/ |
| H A D | INSTALL.lisp | 23 (load "configure.lisp")
32 The configure process can be automated through the use
37 will use the default values for all options and will not
55 (load "generate-sys-proclaim.lisp")
64 (5) Restart Lisp, and load maxima-build.lisp:
66 (load "maxima-build.lisp")
74 (8) Load the compiled Lisp files:
76 (load "maxima-build.lisp")
86 dumping the compiled application as an image that can later be loaded in
|
| /dports/lang/guile/guile-3.0.7/doc/ref/ |
| H A D | api-evaluation.texi | 662 compiled already, so they load and run quickly.
825 want to place a compile file in the @code{%load-compiled-path}, you
860 @deffn {Scheme Procedure} load-compiled filename
864 calling @code{load-compiled} on the resulting file is equivalent to
968 It's better to use @code{add-to-load-path} than to modify
1011 source file, it will also search the @code{%load-compiled-path} for a
1014 using @code{load-compiled}.
1016 @defvar %load-compiled-path
1024 When @code{primitive-load-path} searches the @code{%load-compiled-path}
1262 and @code{load-compiled}. Guile provides another option to compose
[all …]
|
| /dports/x11-toolkits/qt5-declarative/kde-qtdeclarative-5.15.2p41/src/qml/doc/src/qmllanguageref/documents/ |
| H A D | networktransparency.qdoc | 10 ** Licensees holding valid commercial Qt licenses may use this file in
15 ** information use the contact form at https://www.qt.io/contact-us.
54 … QML types themselves can be on the network - if the \l {Prototyping with qmlscene} is used to load
56 will load \tt http://example.com/mystuff/qmldir and resolve the type just as it would for a local f…
57 For example if the qmldir file contains the line "World World.qml", it will load
87 One of the URL schemes built into Qt is the "qrc" scheme. This allows content to be compiled into
89 that is compiled into the executable:
96 The content itself can then use relative URLs, and so be transparently unaware that the content is
97 compiled into the executable.
120 In order to preserve the trust of users, QML application developers should not load
[all …]
|
| /dports/x11-toolkits/qt5-declarative-test/kde-qtdeclarative-5.15.2p41/src/qml/doc/src/qmllanguageref/documents/ |
| H A D | networktransparency.qdoc | 10 ** Licensees holding valid commercial Qt licenses may use this file in
15 ** information use the contact form at https://www.qt.io/contact-us.
54 … QML types themselves can be on the network - if the \l {Prototyping with qmlscene} is used to load
56 will load \tt http://example.com/mystuff/qmldir and resolve the type just as it would for a local f…
57 For example if the qmldir file contains the line "World World.qml", it will load
87 One of the URL schemes built into Qt is the "qrc" scheme. This allows content to be compiled into
89 that is compiled into the executable:
96 The content itself can then use relative URLs, and so be transparently unaware that the content is
97 compiled into the executable.
120 In order to preserve the trust of users, QML application developers should not load
[all …]
|
| /dports/lang/racket/racket-8.3/src/expander/compile/ |
| H A D | form.rkt | 44 #:compiled-expression-callback [compiled-expression-callback void]
59 ;; For each phase, keep track of all compiled expressions for the
204 (compiled-expression-callback e #f phase (as-required? header))
213 (compiled-expression-callback e #f phase (as-required? header))
285 #:load-modules? #f
394 ;; means that the set of imports can change: return a compiled linklet
406 #:load-modules? load-modules?
436 load-modules?
445 (define (make-module-use-to-linklet optimize-linklet? load-modules?
452 (define mod-name (module-path-index-resolve (module-use-module mu*) load-modules?))
[all …]
|
| /dports/lang/racket-minimal/racket-8.3/src/expander/compile/ |
| H A D | form.rkt | 44 #:compiled-expression-callback [compiled-expression-callback void]
59 ;; For each phase, keep track of all compiled expressions for the
204 (compiled-expression-callback e #f phase (as-required? header))
213 (compiled-expression-callback e #f phase (as-required? header))
285 #:load-modules? #f
394 ;; means that the set of imports can change: return a compiled linklet
406 #:load-modules? load-modules?
436 load-modules?
445 (define (make-module-use-to-linklet optimize-linklet? load-modules?
452 (define mod-name (module-path-index-resolve (module-use-module mu*) load-modules?))
[all …]
|
| /dports/www/firefox/firefox-99.0/third_party/rust/mapped_hyph/ |
| H A D | README.md | 7 may be in use by multiple processes.
14 In addition, a compiled dictionary mapped into a shared-memory block
21 mapped_hyph has been created primarily for use by Gecko, replacing the use of libhyphen,
22 and so its features (and limitations) are based on this use case.
31 The compiled hyphenation dictionary format includes provision for replacement
49 See src/ffi.rs for C/C++ APIs that can be used to load hyphenation files
61 (A compiled version of the `hyph_en_US` dictionary from libhyphen is currently
69 it attempts to compress the compiled table by merging duplicate states (which
73 intended for use from Gecko.
|
| /dports/mail/thunderbird/thunderbird-91.8.0/third_party/rust/mapped_hyph/ |
| H A D | README.md | 7 may be in use by multiple processes.
14 In addition, a compiled dictionary mapped into a shared-memory block
21 mapped_hyph has been created primarily for use by Gecko, replacing the use of libhyphen,
22 and so its features (and limitations) are based on this use case.
31 The compiled hyphenation dictionary format includes provision for replacement
49 See src/ffi.rs for C/C++ APIs that can be used to load hyphenation files
61 (A compiled version of the `hyph_en_US` dictionary from libhyphen is currently
69 it attempts to compress the compiled table by merging duplicate states (which
73 intended for use from Gecko.
|
| /dports/www/firefox-esr/firefox-91.8.0/third_party/rust/mapped_hyph/ |
| H A D | README.md | 7 may be in use by multiple processes.
14 In addition, a compiled dictionary mapped into a shared-memory block
21 mapped_hyph has been created primarily for use by Gecko, replacing the use of libhyphen,
22 and so its features (and limitations) are based on this use case.
31 The compiled hyphenation dictionary format includes provision for replacement
49 See src/ffi.rs for C/C++ APIs that can be used to load hyphenation files
61 (A compiled version of the `hyph_en_US` dictionary from libhyphen is currently
69 it attempts to compress the compiled table by merging duplicate states (which
73 intended for use from Gecko.
|
| /dports/lang/racket/racket-8.3/collects/syntax/private/ |
| H A D | modcode-noctc.rkt | 16 default-compiled-sub-path)
24 (let ([d (current-load-relative-directory)])
42 ;; the load-relative directory for unmarshaling
44 (parameterize ([current-load-relative-directory
80 #:roots [root-strs (current-compiled-file-roots)]
94 (define (default-compiled-sub-path)
95 (let ([l (use-compiled-file-paths)])
98 "compiled")))
254 (format "get-module-code: cannot use extension file; ~e" path)
261 (parameterize ([current-load-relative-directory
[all …]
|
| /dports/lang/racket-minimal/racket-8.3/collects/syntax/private/ |
| H A D | modcode-noctc.rkt | 16 default-compiled-sub-path)
24 (let ([d (current-load-relative-directory)])
42 ;; the load-relative directory for unmarshaling
44 (parameterize ([current-load-relative-directory
80 #:roots [root-strs (current-compiled-file-roots)]
94 (define (default-compiled-sub-path)
95 (let ([l (use-compiled-file-paths)])
98 "compiled")))
254 (format "get-module-code: cannot use extension file; ~e" path)
261 (parameterize ([current-load-relative-directory
[all …]
|
| /dports/textproc/kibana6/kibana-6.8.16-darwin-x86_64/node_modules/terser/node_modules/source-map-support/ |
| H A D | README.md | 29 node -r source-map-support/register compiled.js
94 if (source === 'compiled.js') {
135 compiled.js:
142 //# sourceMappingURL=compiled.js.map
145 compiled.js.map:
150 "file": "compiled.js",
157 Run compiled.js using node (notice how the stack trace uses original.js instead of compiled.js):
160 $ node compiled.js
169 at Module.load (module.js:356:32)
206 at Module.load (module.js:356:32)
[all …]
|
| /dports/textproc/kibana6/kibana-6.8.16-darwin-x86_64/node_modules/graphql-extensions/node_modules/source-map-support/ |
| H A D | README.md | 29 node -r source-map-support/register compiled.js
94 if (source === 'compiled.js') {
135 compiled.js:
142 //# sourceMappingURL=compiled.js.map
145 compiled.js.map:
150 "file": "compiled.js",
157 Run compiled.js using node (notice how the stack trace uses original.js instead of compiled.js):
160 $ node compiled.js
169 at Module.load (module.js:356:32)
206 at Module.load (module.js:356:32)
[all …]
|
| /dports/www/chromium-legacy/chromium-88.0.4324.182/third_party/llvm/llvm/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|
| /dports/devel/llvm-cheri/llvm-project-37c49ff00e3eadce5d8703fdc4497f28458c64a8/llvm/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|
| /dports/devel/llvm10/llvm-10.0.1.src/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|
| /dports/devel/wasi-libcxx/llvm-project-13.0.1.src/llvm/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|
| /dports/graphics/llvm-mesa/llvm-13.0.1.src/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|
| /dports/devel/llvm12/llvm-project-12.0.1.src/llvm/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|
| /dports/devel/llvm11/llvm-11.0.1.src/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|
| /dports/devel/llvm-devel/llvm-project-f05c95f10fc1d8171071735af8ad3a9e87633120/llvm/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|
| /dports/devel/wasi-compiler-rt13/llvm-project-13.0.1.src/llvm/test/CodeGen/AArch64/ |
| H A D | machine-outliner-noredzone.ll | 4 ; Ensure that the MachineOutliner does not fire on functions which use a
14 ; *know* we don't use a redzone. The GHC calling convention is one of these
21 %1 = load i32, i32* @x, align 4
25 %3 = load i32, i32* @x, align 4
29 %5 = load i32, i32* @x, align 4
35 ; foo() should have a redzone when compiled with -aarch64-redzone, and no
50 %5 = load i32, i32* %1, align 4
53 %7 = load i32, i32* %3, align 4
56 %9 = load i32, i32* %4, align 4
59 %11 = load i32, i32* %2, align 4
[all …]
|