aboutsummaryrefslogtreecommitdiff
path: root/gcc/rust/backend/rust-compile-context.h
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-06-19 20:25:18 +0000
committerGitHub <noreply@github.com>2021-06-19 20:25:18 +0000
commit4f31d4bbe9ca68aebc05fd12be2751c32c25a9d7 (patch)
tree0f10f768a567deeccd6bcc50c4c121bb70a3cd70 /gcc/rust/backend/rust-compile-context.h
parentace501018b5a3eedc545711814aad14149d16395 (diff)
parent213b638b3269078d77f02a46602105917616372f (diff)
parentc143022ebee18a2d32d2844521d5ec1f0b06bdb6 (diff)
parent09d26b3e0b11859bc9fa27f9a4b176da47bc7add (diff)
downloadgcc-4f31d4bbe9ca68aebc05fd12be2751c32c25a9d7.zip
gcc-4f31d4bbe9ca68aebc05fd12be2751c32c25a9d7.tar.gz
gcc-4f31d4bbe9ca68aebc05fd12be2751c32c25a9d7.tar.bz2
Merge #506 #507 #508
506: Fix: do not use object after it has been moved r=philberty a=dkm After std::move(mapping), mapping is unspecified <!-- THIS COMMENT IS INVISIBLE IN THE FINAL PR, BUT FEEL FREE TO REMOVE IT Thank you for making Rust GCC better! If your PR fixes an issue, you can add "Fixes #issue_number" into this PR description and the git commit message. This way the issue will be automatically closed when your PR is merged. If your change addresses an issue but does not fully fix it please mark it as "Addresses #issue_number" in the git commit message. Here is a checklist to help you with your PR. - \[ ] GCC code require copyright assignment: https://gcc.gnu.org/contribute.html - \[ ] Read contributing guidlines - \[ ] `make check-rust` passes locally - \[ ] Run `clang-format` - \[ ] Added any relevant test cases to `gcc/testsuite/rust/` Note that you can skip the above if you are just opening a WIP PR in order to get feedback. --- --> 507: Add more info in HIR dump for struct r=philberty a=dkm Make struct fields more visible in dumps and add the mapping in the dump string. <!-- THIS COMMENT IS INVISIBLE IN THE FINAL PR, BUT FEEL FREE TO REMOVE IT Thank you for making Rust GCC better! If your PR fixes an issue, you can add "Fixes #issue_number" into this PR description and the git commit message. This way the issue will be automatically closed when your PR is merged. If your change addresses an issue but does not fully fix it please mark it as "Addresses #issue_number" in the git commit message. Here is a checklist to help you with your PR. - \[ ] GCC code require copyright assignment: https://gcc.gnu.org/contribute.html - \[ ] Read contributing guidlines - \[ ] `make check-rust` passes locally - \[ ] Run `clang-format` - \[ ] Added any relevant test cases to `gcc/testsuite/rust/` Note that you can skip the above if you are just opening a WIP PR in order to get feedback. --- --> 508: Make 3 error messages slightly more informational r=philberty a=dkm Add more context to some internal error messages (ie. not intended for user) <!-- THIS COMMENT IS INVISIBLE IN THE FINAL PR, BUT FEEL FREE TO REMOVE IT Thank you for making Rust GCC better! If your PR fixes an issue, you can add "Fixes #issue_number" into this PR description and the git commit message. This way the issue will be automatically closed when your PR is merged. If your change addresses an issue but does not fully fix it please mark it as "Addresses #issue_number" in the git commit message. Here is a checklist to help you with your PR. - \[ ] GCC code require copyright assignment: https://gcc.gnu.org/contribute.html - \[ ] Read contributing guidlines - \[ ] `make check-rust` passes locally - \[ ] Run `clang-format` - \[ ] Added any relevant test cases to `gcc/testsuite/rust/` Note that you can skip the above if you are just opening a WIP PR in order to get feedback. --- --> Co-authored-by: Marc Poulhiès <dkm@kataplop.net>