Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

NamedRegionTimer is not thread safe #44417

Open
llvmbot opened this issue Mar 1, 2020 · 0 comments
Open

NamedRegionTimer is not thread safe #44417

llvmbot opened this issue Mar 1, 2020 · 0 comments
Labels
bugzilla Issues migrated from bugzilla llvm Umbrella label for LLVM issues

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Mar 1, 2020

Bugzilla Link 45072
Version trunk
OS Linux
Reporter LLVM Bugzilla Contributor

Extended Description

The NamedRegionTimer obtains a timer instance from NamedRegionTimers global,
which keeps a single timer per timer name and timer group name. Those names are
generally constants and a single timer might end up being used from multiple
threads:

Assertion `!Running && "Cannot start a running timer"' failed.

This affects rustc -Z time-llvm-passes when compiling with multiple codegen units.

Downstream bug reports:
@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 10, 2021
@Endilll Endilll added the llvm Umbrella label for LLVM issues label Sep 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla llvm Umbrella label for LLVM issues
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Endilll @llvmbot