Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

ziglang / zig Public

Notifications You must be signed in to change notification settings
Fork 2.6k
Star 36.4k

Code
Issues 3.1k
Pull requests 249
Actions
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Wiki
Security
Insights

Support running LLVM backend in a separate thread#21068

Open

antlilja wants to merge 5 commits intoziglang:masterziglang/zig:masterfrom antlilja:llvm-seperate-threadantlilja/zig:llvm-seperate-threadCopy head branch name to clipboard

+644-613

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Dec 26, 2024

LLVM: Move pt field from Object to NavGen
antlilja
committed
LLVM: Pass correct tid to emit
antlilja
committed
Store stack trace type in Zcu
antlilja
committed
LLVM: Enable running in a seperate thread
antlilja
committed
Don't use pt.errorIntType in LLVM backend
antlilja
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.