Now that write data continuously into the memory mapping, we don't need
to keep the VMO handle around after it has been mapped. This change also
ensures that the VMO is always closed on error.
Details
Details
- Reviewers
mcgrathr - Commits
- rG485862ecdac4: [profile] Avoid duplicating or leaking VMO
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
lgtm
compiler-rt/lib/profile/InstrProfilingPlatformFuchsia.c | ||
---|---|---|
181 | s/closes/consumes/ (the API just says it takes ownership, you don't know whether it remains a valid handle or not) |
s/closes/consumes/ (the API just says it takes ownership, you don't know whether it remains a valid handle or not)