File: README.md

package info (click to toggle)
chromium 139.0.7258.127-1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,068 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (45 lines) | stat: -rw-r--r-- 1,213 bytes parent folder | download | duplicates (8)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
# Handle to DirectHandle migration tool

A clang tool for the migration of `v8::internal::Handle<T>` to
`v8::internal::DirectHandle<T>`. This is only useful for the V8 code base,
as such handles can only be used there. The two types are only different
in builds with `v8_enable_direct_handle=true`, which implies
`v8_enable_conservative_stack_scanning=true`, so the tool should be applied
to such a debug build.

## Building

The first time, build with:
```
tools/clang/scripts/build.py --without-android --without-fuchsia --extra-tools v8_handle_migrate
```
Then, recompile with:
```
ninja -C third_party/llvm-build/Release+Asserts v8_handle_migrate
```

## Usage

Build the release with which to use it (see above for GN args), e.g.:
```
autoninja -C out/css all
```

You may need to generate the database of compile commands:
```
tools/clang/scripts/generate_compdb.py -p out/css -o out/css/compile_commands.json
```

Then, process files with:
```
tools/clang/scripts/run_tool.py --tool v8_handle_migrate -p out/css files.cpp
```

## Testing

Run the tests with:
```
tools/clang/scripts/test_tool.py v8_handle_migrate --apply-edits
```

Notice that the tests use mock versions of the relevant V8 header files.