multiversion VS llvm-project

Not sure if it will help you. But this looks like crate you can use https://github.com/calebzulawski/multiversion

LogInit: Compiled with Clang: 10.0.1 (https://github.com/llvm/llvm-project ef32c611aa214dea855364efd7ba451ec5ec3f74)

Couple ways, for example on the github page [1] , click the "tags" link [2] above the file list, find the tag for release 14.0.0, which is llvmorg-14.0.0, and now you can do any commit operation with that name instead of a commit.

If you have a checkout, you can find the tag name by doing a git tag -l *14* and looking through the output; I'm intentionally providing a very general glob because one may not know beforehand their exact tag name conventions.

[1] https://github.com/llvm/llvm-project

[2] https://github.com/llvm/llvm-project/tags

clang (It is very similar to gcc, which many tutorials reccomend. You can get it here: https://github.com/llvm/llvm-project/releases/tag/llvmorg-14.0.0 [ see: LLVM-14.0.0-win64.exe ]

Interesting! What is your take on TinyGo. How does the LLVM compiler compare to say something you are familiar with, i.e. gcc? Would it be comparable?

Locating this kind of bug usually starts innocently, by commenting out various places of your own code, then analyzing your program under a debugger only to find yourself doing git clone https://github.com/llvm/llvm-project a few hours later 😅

> Should I report it somewhere?

Please do. You can open an issue (Bugzilla has been deprecated) on LLVM's github repo: https://github.com/llvm/llvm-project

Here is what Clang thinks: https://github.com/llvm/llvm-project/blob/589b9df4e15131348b...

parens: ()

squares: []

braces: {}

basically a mixed of British and American English

Apple | Debugger Engineer | Full-time | Onsite | Cupertino

The LLDB team at Apple is looking for an engineer to work on the LLDB debugger. LLDB is a core part of Apple's developer tools, used internally to debug Apple's software stack and externally by millions of developers. You’ll be able to work on different levels of the stack: from supporting our existing and upcoming platforms to developing new features to make debugging even better. Most of your work will be open source, on llvm.org (http://llvm.org/) and github.com (http://github.com/) where you’ll collaborate with the LLVM and Swift community.

If you love working on low-level tools you should check out the details here: https://jobs.apple.com/en-us/details/200311412/debugger-engi...