llvm-project VS gcc

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...

% emcc -v emcc (Emscripten gcc/clang-like replacement + linker emulating GNU ld) 3.1.8-git clang version 15.0.0 (https://github.com/llvm/llvm-project.git 80ec0ebfdc5692a58e0832125f2c6a991df9d63f) Target: wasm32-unknown-emscripten Thread model: posix InstalledDir: /usr/local/Cellar/emscripten/3.1.8/libexec/llvm/bin

clang + lldb for getting work done

> the terribleness of exceptions is way overhyped

It's not that exceptions are terrible. I have nothing against them. The thing is that most of the time they are not affordable, especially in embedded. Some compilers don't even support them (some 8-bit IIRC). Most (including mine) embedded C++ programs have exceptions disabled.

> return a `std::optional`

The same goes for std. I don't know the overhead of possibly duplicating these classes(1) for every instance of std::optional. Most (including mine) embedded C++ programs don't use std.

30KB of extra code is nothing for desktop/server applications, but it's not convenient for a MCU with 64KB of flash.

(1): https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-...

> just use a factory function instead

This is practical with an efficient heap allocator (which I might not have). What happens if I want a scoped (on stack) instance of a class?

See how things are quickly getting more complicated with C++?

Good news, GCC 12.1 is expected to be released in this week or in early May. https://gcc.gnu.org/ https://github.com/gcc-mirror/gcc/commit/091e10203846812c4e98b465ddfb36d12f146be8 (bumped the version into 13.0.0)

Ohh, I missed it, GCC did the mass rename after all: https://github.com/gcc-mirror/gcc/commit/5c69acb32329d49e58c26fa41ae74229a52b9106

True; I probably overstated it in terms of idiom recognition (compiler enthusiast, but by no means expert). I suspect that a similar SSA or data flow analysis combined with some judicious rewrite rules like (X ^ Y) ^ Y -> X [0] are enough for the xor swap trick as well.

[0] https://github.com/gcc-mirror/gcc/blob/9fdac7e16c940fb6264e6...

gcc: https://github.com/gcc-mirror/gcc

There might have been other code / files they were using incorrectly of course, but at least the ppu_intrinsics.h file that I believe was specifically originally in question there comes directly from GCC, not any kind of Sony SDK.