| /dports/lang/rust/rustc-1.58.1-src/compiler/rustc_codegen_cranelift/docs/ |
| H A D | usage.md | 3 rustc_codegen_cranelift can be used as a near-drop-in replacement for `cargo build` or `cargo run` …
9 In the directory with your project (where you can do the usual `cargo build`), run:
29 In jit mode cg_clif will immediately execute your code without creating an executable file.
32 > The jit mode will probably need cargo integration to make this possible.
35 $ $cg_clif_dir/build/cargo jit
41 $ $cg_clif_dir/build/bin/cg_clif -Zunstable-features -Cllvm-args=mode=jit -Cprefer-dynamic my_crate…
44 There is also an experimental lazy jit mode. In this mode functions are only compiled once they are
48 $ $cg_clif_dir/build/cargo lazy-jit
53 These are a few functions that allow you to easily run rust code from the shell using cg_clif as ji…
60 function jit() {
[all …]
|
| /dports/devel/aarch64-none-elf-gcc/gcc-8.4.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc9/gcc-9.4.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/devel/avr-gcc/gcc-10.2.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/devel/riscv64-gcc/gcc-8.3.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc11-devel/gcc-11-20211009/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/devel/riscv32-unknown-elf-gcc/gcc-8.4.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/devel/arm-none-eabi-gcc/gcc-8.4.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/devel/riscv64-none-elf-gcc/gcc-8.4.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc9-aux/gcc-9.1.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/misc/cxx_atomics_pic/gcc-11.2.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc10/gcc-10.3.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc9-devel/gcc-9-20211007/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc8/gcc-8.5.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc11/gcc-11.2.0/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc10-devel/gcc-10-20211008/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc12-devel/gcc-12-20211205/gcc/jit/docs/internals/ |
| H A D | index.rst | 106 The test executables are normally deleted after each test is run. For
114 which can be run independently.
116 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
200 The library uses a driver executable for converting from .s assembler
207 locate this executable.
209 The executable is normally installed to the installation bindir
216 The driver executable invokes the linker, and the latter needs to locate
356 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
358 in your email (along with the host triple that the tests were run on).
414 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gnat_util/gcc-6-20180516/gcc/jit/docs/internals/ |
| H A D | index.rst | 112 which can be run independently.
114 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
196 The library uses a driver executable for converting from .s assembler
203 locate this executable.
205 The executable is normally installed to the installation bindir
212 The driver executable invokes the linker, and the latter needs to locate
226 For example, to run a binary that uses the library against a non-installed
352 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
354 in your email (along with the host triple that the tests were run on).
410 to being run standalone, they also get run within
[all …]
|
| /dports/lang/gcc6-aux/gcc-6-20180516/gcc/jit/docs/internals/ |
| H A D | index.rst | 112 which can be run independently.
114 You can compile and run individual tests by passing "jit.exp=TESTNAME" to RUNTESTFLAGS e.g.:
196 The library uses a driver executable for converting from .s assembler
203 locate this executable.
205 The executable is normally installed to the installation bindir
212 The driver executable invokes the linker, and the latter needs to locate
226 For example, to run a binary that uses the library against a non-installed
352 ``jit`` and ``testsuite/jit.dg`` subdirectories. However, please run
354 in your email (along with the host triple that the tests were run on).
410 to being run standalone, they also get run within
[all …]
|
| /dports/www/firefox/firefox-99.0/js/src/doc/ |
| H A D | test.rst | 8 …rMonkey also has a large collection of internal tests. These tests are run using ``mach jit-test``.
10 Both sets of tests can be run from a normal build of the JS shell.
42 The Test262 tests can also be run in the browser, using:
52 Running jit-tests locally
55 The jit-test shell harness is in ``js/src/jit-test/jit_test.py``. It can be invoked using
59 ./mach jit-test
65 ./mach jit-test TEST_PATH_SUBSTRING [TEST_PATH_SUBSTRING_2 ...]
67 … option allows you to test the JS executable with different flags. The flags are used to control w…
69 …jit-tests`` is ``-R <filename>`` (or ``--retest <filename>``). The first time this is run, it runs…
79 Adding new jit-tests
[all …]
|
| /dports/sysutils/vector/lucet-d4fc14a03bdb99ac83173d27fddf1aca48412a86/wasmtime/docs/ |
| H A D | contributing-building.md | 3 This section describes everything required to build and run Wasmtime.
36 of the repository and run this command:
42 The built executable will be located at `target/debug/wasmtime`.
44 To make an optimized build, run this command in the root of the repository:
50 The built executable will be located at `target/release/wasmtime`.
53 with `cargo run`.
57 To build the C API of Wasmtime you can run:
71 the `cargo build` invocation. For example, to build the `wasmtime-jit` crate,
75 cargo build -p wasmtime-jit
82 cd crates/jit/
[all …]
|
| H A D | examples-profiling-vtune.md | 3 …ersion is appropriate for detailed analysis of your WASM program. Note for jit support, Wasmtime o…
5 …jit profiling APIs at [`https://github.com/intel/ittapi`](https://github.com/intel/ittapi). These …
7 For jit profiling with VTune Profiler, first you want to make sure the `vtune` feature is enabled. …
26 $ amplxe-cl -run-pass-thru=--no-altstack -collect hotspots target/debug/wasmtime --vtune foo.wasm
29 … so that the collector is also alerted to jit events that take place during runtime. The first tim…
51 on certain types of analysis. Below we show a command line executable option using amplxe-cl, which…
57 $ amplxe-cl -run-pass-thru=--no-altstack -v -collect hotspots target/debug/wasmtime --vtune fib.wasm
|
| /dports/lang/erlang-runtime24/otp-OTP-24.1.7/erts/emulator/internal_doc/ |
| H A D | BeamAsm.md | 14 in run-time. Only small parts of the
204 executable page and once with a writable page. Since they're backed by the
205 same memory, writes to the writable page appear magically in the executable
341 ## run stackcollapse
352 not need the symbols in the executable.
373 run you would do this:
381 `perf inject --jit` like this:
395 > time or you may run out of inodes.
427 * You do not have an OS that supports executable *and* writable memory
429 If you run `./configure --enable-jit` configure will abort when it discovers that
[all …]
|
| /dports/lang/erlang-wx/otp-OTP-24.1.7/erts/emulator/internal_doc/ |
| H A D | BeamAsm.md | 14 in run-time. Only small parts of the
204 executable page and once with a writable page. Since they're backed by the
205 same memory, writes to the writable page appear magically in the executable
341 ## run stackcollapse
352 not need the symbols in the executable.
373 run you would do this:
381 `perf inject --jit` like this:
395 > time or you may run out of inodes.
427 * You do not have an OS that supports executable *and* writable memory
429 If you run `./configure --enable-jit` configure will abort when it discovers that
[all …]
|
| /dports/lang/erlang/otp-OTP-24.1.7/erts/emulator/internal_doc/ |
| H A D | BeamAsm.md | 14 in run-time. Only small parts of the
204 executable page and once with a writable page. Since they're backed by the
205 same memory, writes to the writable page appear magically in the executable
341 ## run stackcollapse
352 not need the symbols in the executable.
373 run you would do this:
381 `perf inject --jit` like this:
395 > time or you may run out of inodes.
427 * You do not have an OS that supports executable *and* writable memory
429 If you run `./configure --enable-jit` configure will abort when it discovers that
[all …]
|