You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- IRC: Join us on [IRC](https://web.libera.chat/#rustc_codegen_gcc)
22
-
- GitHub Issues: For bug reports and feature discussions
22
+
-[GitHub Issues](https://github.com/rust-lang/rustc_codegen_gcc/issues): For bug reports and feature discussions
23
23
24
24
We encourage new contributors to join our communication channels and introduce themselves. Feel free to ask questions about where to start or discuss potential contributions.
25
25
@@ -28,12 +28,15 @@ We encourage new contributors to join our communication channels and introduce t
28
28
### Common Development Tasks
29
29
30
30
#### Running Specific Tests
31
+
31
32
To run specific tests, use appropriate flags such as:
33
+
32
34
-`./y.sh test --test-libcore`
33
35
-`./y.sh test --std-tests`
34
36
-`cargo test -- <name of test>`
35
37
36
38
Additionally, you can run the tests of `libgccjit`:
39
+
37
40
```bash
38
41
# libgccjit tests
39
42
cd gcc-build/gcc
@@ -43,8 +46,10 @@ make check-jit RUNTESTFLAGS="-v -v -v jit.exp=jit.dg/test-asm.cc"
43
46
```
44
47
45
48
#### Debugging Tools
49
+
46
50
The project provides several environment variables for debugging:
@@ -54,18 +59,21 @@ Full list of debugging options can be found in the [README](Readme.md#env-vars).
54
59
## Making Contributions
55
60
56
61
### Finding Issues to Work On
62
+
57
63
1. Look for issues labeled with [`good first issue`](https://github.com/rust-lang/rustc_codegen_gcc/issues?q=is%3Aissue%20state%3Aopen%20label%3A"good%20first%20issue") or [`help wanted`](https://github.com/rust-lang/rustc_codegen_gcc/issues?q=is%3Aissue%20state%3Aopen%20label%3A"help%20wanted")
58
64
2. Check the [progress report](https://blog.antoyo.xyz/rustc_codegen_gcc-progress-report-34#state_of_rustc_codegen_gcc) for larger initiatives
59
65
3. Consider improving documentation or investigating [failing tests](https://github.com/rust-lang/rustc_codegen_gcc/tree/master/tests) (except `failing-ui-tests12.txt`)
60
66
61
67
### Pull Request Process
68
+
62
69
1. Fork the repository and create a new branch
63
70
2. Make your changes with clear commit messages
64
71
3. Add tests for new functionality
65
72
4. Update documentation as needed
66
73
5. Submit a PR with a description of your changes
67
74
68
75
### Code Style Guidelines
76
+
69
77
- Follow Rust standard coding conventions
70
78
- Ensure your code passes `rustfmt` and `clippy`
71
79
- Add comments explaining complex logic, especially in GCC interface code
Copy file name to clipboardExpand all lines: Readme.md
+6-4
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,13 @@ You need to use my [fork of gcc](https://github.com/rust-lang/gcc) which already
19
19
The default configuration (see below in the [Quick start](#quick-start) section) will download a `libgccjit` built in the CI that already contains these patches, so you don't need to build this fork yourself if you use the default configuration.
20
20
21
21
### Dependencies
22
-
- rustup: follow instructions on the [official website](https://rustup.rs)
23
-
- consider to install DejaGnu which is necessary for running the libgccjit test suite. [website](https://www.gnu.org/software/dejagnu/#downloading)
*_**CG_GCCJIT_DUMP_ALL_MODULES**_: Enables dumping of all compilation modules. When set to "1", a dump is created for each module during compilation and stored in `/tmp/reproducers/`.
163
165
*_**CG_GCCJIT_DUMP_MODULE**_: Enables dumping of a specific module. When set with the module name, e.g., `CG_GCCJIT_DUMP_MODULE=module_name`, a dump of that specific module is created in `/tmp/reproducers/`.
0 commit comments